COLORADO SPRINGS, CO: $32.1M on 166,333 FEC receipts

High volume on a $32 million book

One hundred sixty-six thousand three hundred thirty-three lines produce $32,129,291. Divide the pair and the mean itemized line is about $193. That mean is arithmetic from the two packet facts. The shape is many receipts, a modest average. FEC.gov does not publish a median or a unique-donor count on this city aggregate.

Denver, Pueblo, and Fort Collins keep separate Colorado hubs. They are not inside $32,129,291 unless the filer typed COLORADO SPRINGS. El Paso County is orientation, not an FEC roll-up.

Springs, not Denver

Colorado Springs is not a Denver suburb in the FEC city field. This packet publishes COLORADO SPRINGS, CO only: $32,129,291 and 166,333 lines. Adding Denver would be a recode.

State CO on the key is required in the citation. Recheck both facts on the live hub if a later extract lands.

City string versus postal map

FEC.gov stores whatever city appeared on the itemized receipt. COLORADO SPRINGS plus CO is the match. Recoding into a Census place or a Front Range label is a different dataset.

ZIP pages cut the same federal series by postal code. Summing Pikes Peak ZIPs can diverge from $32,129,291 when some receipts used Monument or Manitou Springs as the city. The 166,333-line count follows the city field.

Limits of the Colorado Springs aggregate

Colorado state campaigns file under state law. Those receipts are outside $32,129,291 and outside 166,333. Unitemized federal gifts are omitted. Independent expenditures that never appear as contribution itemizations are outside both facts.

Nothing here estimates how Colorado Springs voted. Occupation and recipient live on other FEC fields. Use the city table, then ZIP pages, then the cities index.

Citing COLORADO SPRINGS, CO

Name FEC.gov, name contributor city, and print $32,129,291 with 166,333 together. Dropping the line count hides the volume that produces a mean near $193.

Office addresses can share the Colorado Springs city field with household streets. Totals can include a PAC or joint-fundraising address when that is what filers typed. The 166,333 lines are receipts, not unique persons. If the live hub disagrees with this snapshot, trust the hub. Open original reports on FEC.gov when a named Colorado Springs receipt matters.

How researchers should use the Colorado Springs hub

Start on the live Colorado Springs city page, then open ZIP pages if a postal cut is the real question. $32,129,291 is the city-string dollar total in this snapshot. 166,333 is the matching line count. Those two numbers move together when FEC.gov amends a receipt. They do not move because a researcher prefers Denver as the “real” Front Range. Filers typed COLORADO SPRINGS. LobbyVault indexed COLORADO SPRINGS.

A mean near $193 is only $32,129,291 divided by 166,333. The large line count is the shape of this extract. Occupation, recipient, and party are different FEC fields. None of those fields are in this packet. Do not infer turnout from the 166,333 rows. Cite the pair: contributor city COLORADO SPRINGS, CO, $32,129,291, 166,333 itemized federal contributions, source FEC.gov via LobbyVault. Colorado non-federal filings never enter either fact.

El Paso County and the Pikes Peak region are map labels. Monument, Manitou Springs, and Fountain remain separate city strings. $32,129,291 does not include them unless the filer typed COLORADO SPRINGS. The 166,333 lines are the high-volume end of this dollar band. The mean near $193 follows from that volume.

Do not treat 166,333 as unique persons. Do not treat the mean as typical. Denver is a different hub. Recheck both facts on the live page. Colorado non-federal filings, unitemized gifts, and independent expenditures that are not contribution itemizations stay outside. Cite COLORADO SPRINGS, CO with $32,129,291 and 166,333 together.

Colorado Springs carries 166,333 lines on $32,129,291, the largest line count in this dollar band. That is why the mean sits near $193. Volume is not turnout. Volume is not unique donors. Denver is a different city string. El Paso County is a map, not an FEC roll-up. Cite COLORADO SPRINGS, CO with both packet facts. Recheck the live hub after any FEC.gov amendment.

Keep COLORADO SPRINGS, CO, $32,129,291, and 166,333 in one citation. The mean near $193 is those two numbers divided. Denver remains a separate string. Pueblo remains a separate string. El Paso County remains a map. Colorado non-federal filings remain outside. Unitemized federal gifts remain outside. Independent expenditures that are not contribution itemizations remain outside. Start on the live city page. Open ZIP pages for a postal cut. Open FEC.gov for a named Colorado Springs receipt. Do not convert 166,333 lines into unique persons or into turnout.

Questions

What is Colorado Springs’ federal contribution total on LobbyVault?

Itemized FEC.gov receipts listing contributor city COLORADO SPRINGS, CO total $32,129,291 across 166,333 contributions. That pair is a city-string roll-up of federal Schedule A rows, not a unique-donor count and not a census of Colorado Springs residents. Unitemized gifts sit outside both figures.

Why is the Colorado Springs mean near $193?

Divide $32,129,291 by 166,333 and the arithmetic mean is about $193. The line count is large relative to the dollar book. That is a shape fact, not a typical gift. This packet publishes no unique-donor figure and no median.

Does Colorado Springs’ total include Denver or Pueblo?

Only if the filer typed COLORADO SPRINGS. Denver, Pueblo, and Fort Collins are separate city strings when they appear that way on the receipt. $32,129,291 is the COLORADO SPRINGS, CO match. The 166,333 lines follow the same rule. El Paso County is not an FEC dimension on this hub.

Where do the Colorado Springs facts come from?

Both facts come from FEC.gov itemized contribution aggregates indexed on LobbyVault: $32,129,291 and 166,333 lines. Original reports remain on FEC.gov. Colorado non-federal filings are outside the pair. If a later extract disagrees, the Commission’s filing controls. The mean of about $193 is arithmetic from those two packet numbers.