VANCOUVER, WA: $24.2M on 140,537 FEC receipts

140,537 lines behind $24,195,449

Vancouver, WA, shows 140,537 itemizations behind $24,195,449. That mix is a high-volume, smaller-average file. Many of the lines will be modest individual receipts that happen to share the Vancouver city field. Committee receipts that list a Vancouver address still sit in the same column. LobbyVault does not strip one type before adding the dollars.

Portland, OR, Camas, and Battle Ground are stored as their own city strings. They are not folded into this total. Totals can include PAC and joint-fundraising addresses, not only residents. Read $24,195,449 as tagged federal receipts, not as what Vancouver residents gave. The 140,537 lines are disclosed transactions, not unique persons.

Nothing on this page estimates how Vancouver voted, which candidates the receipts supported, or whether a listed street is a home. Occupation and recipient committee live on other FEC fields. The supported path is the Vancouver city table, then ZIP pages, then the cities index.

State WA keeps Vancouver off British Columbia

Committees type the city as it appears on the contributor record and the state as WA. A workplace in Vancouver and a home in Portland, OR, can produce different city strings on different receipts. This hub holds only the 140,537 lines labeled VANCOUVER with state WA. That split is disclosure mechanics, not a statement about the Portland metro’s civic identity.

Keeping both facts in view—$24,195,449 and 140,537 contributions—shows a thick file. A combined Portland–Vancouver picture requires adding other hubs by design. Canadian filings are outside FEC.gov.

ZIP codes inside the Vancouver, WA string

140,537 city-field lines can spread across many ZIPs or cluster in a few. This packet does not list those ZIPs. Open the ZIP directory and the live Vancouver hub rather than guessing the split.

After an amendment wave, recheck both the city hub and any ZIP you compared. Snapshots drift independently.

Washington state campaign accounts are not inside $24,195,449. This hub is federal itemizations labeled VANCOUVER, WA: 140,537 records. A metro briefing that blends Portland, OR, is a different object unless those labels are added on purpose.

Vancouver’s volume shape versus Portland, OR

A mean near $172 on 140,537 rows is a volume shape: many itemized lines, smaller average receipt. Volume is not turnout and is not a unique-donor count.

Portland, OR, is a different city key with its own line count. Vancouver’s $24,195,449 is not a subset of Portland and is not interchangeable with it.

Columbia River geography orients readers; this packet has no employer or industry split. Cite the city string and state WA, not the metro brand.

What this packet does not say about Vancouver

Party split, unique donors, and top committees are absent. If a briefing invents those figures for Vancouver, they did not come from this extract.

Independent expenditures that mention a Vancouver-area race can be paid by a committee with a different city on its own reports. Those disbursements do not move $24,195,449.

Citing VANCOUVER, WA from FEC.gov

A mean of about $172 is division of $24,195,449 by 140,537. It is fair to report as arithmetic. It is not fair to report as a typical resident of Vancouver.

Internal links on this page go only to the Vancouver city hub, the all-cities directory, and the ZIP directory. Those are the three paths that match this packet.

Vancouver’s $24,195,449 across 140,537 contributions is a high-volume Clark County city field, mean near $172. Portland, OR, is across the river and separate on the FEC key. Camas and Battle Ground are other strings. Repeat gifts add rows. State-office receipts are omitted. Cite $24,195,449 with 140,537 from FEC.gov aggregates indexed on LobbyVault.

Researchers citing Vancouver, Washington, should keep Portland, Oregon, and British Columbia off the sentence unless they add those objects on purpose. The live Vancouver table can show named committees that this snapshot does not list. A later FEC extract can move $24,195,449 or 140,537 without this guide rewriting itself. Treat the mean near $172 as division only. Washington state-office receipts sit outside both packet facts. If a ZIP page for a Vancouver code disagrees with the city hub, quote both keys rather than forcing a match. Camas and Battle Ground remain other strings. The 140,537-line count still is not a headcount of Vancouver people.

Questions

How much federal campaign money is tied to Vancouver, WA?

FEC.gov itemized receipts listing contributor city VANCOUVER, WA total $24,195,449 across 140,537 contributions in the LobbyVault aggregate. That figure is a city-string roll-up of federal Schedule A rows, not a unique-donor count and not Vancouver, British Columbia. Unitemized gifts sit outside it.

Is Vancouver, WA merged with Portland, OR on this page?

No. LobbyVault counts 140,537 itemized contributions for VANCOUVER, WA against $24,195,449, a mean near $172. Portland, OR, is a different city string. Repeat gifts, redesignations, and memo entries can add rows without adding new donors. A high line count with a modest mean is a volume book, not a turnout score.

Does the Vancouver total include only residents?

No. The city is the contributor-city value on the FEC itemization. Filers typed VANCOUVER with state WA. Office addresses and mail that list Vancouver can be part of $24,195,449 when that is the city string on the receipt. LobbyVault does not recode the field into a residential-only book. The 140,537-line count follows the same rule.

Are Vancouver, WA numbers from FEC.gov?

The numbers come from FEC.gov itemized contribution aggregates indexed on LobbyVault: $24,195,449 and 140,537 lines for VANCOUVER, WA. Original reports remain on FEC.gov. Unitemized federal gifts and non-federal filings from WA are outside both figures. If a later extract disagrees with this snapshot, the Commission’s filing controls. The mean of about $172 is arithmetic from those two packet facts.