BELLEVUE, WA: $96.1M on 245,666 FEC receipts

$96,131,734 is a Schedule A city total

FEC.gov indexed 245,666 itemized rows to contributor city BELLEVUE, WA. Their sum is $96,131,734. The mean near $391 describes the average row, not a household and not a census tract.

King County’s Bellevue string is east of Seattle as geography. Seattle is a different FEC city key. The 245,666-line count is a contribution-line total. It is not a headcount of Bellevue residents. The city total can include a PAC or joint-fundraising committee address when that is the city filers typed. LobbyVault does not recode those rows out of the city string.

If a newsroom map paints Bellevue together with Seattle and Kirkland, the FEC file still splits them. Redmond too. This extract’s only city total is $96,131,734 on 245,666 BELLEVUE, WA rows, mean near $391.

How to read the WA city key for Bellevue

City-name spelling is part of the key. BELLEVUE with state WA is the unit. A close spelling, a neighborhood abbreviation, or a merged metro label is a different aggregate if FEC stored it differently.

Independent expenditures that mention a Bellevue race can be paid by a committee with a different city on its own reports. Those disbursements do not move $96,131,734. Keep independent-expenditure tables separate from this city total.

Using ZIP pages without breaking $96,131,734

If a ZIP page and the Bellevue city page disagree in implied geography, that is expected. They answer different questions: five-digit code versus city string.

Named receipts on the Bellevue FEC page are the next click for researchers who need committee names. This guide does not invent those names.

The Bellevue city key will not absorb nearby towns because a map looks contiguous. Annexation, CDPs, and neighborhood names are not auto-merged. BELLEVUE, WA is the filed string. $96,131,734 belongs to that string alone in this extract.

Postal confusion with Seattle, Kirkland, or Redmond is why the city field is a poor residency proxy. $96,131,734 counts rows that stored BELLEVUE, WA in state WA. 245,666 lines. About $391 each. Neighbor names need their own hubs.

Volume and average on the Bellevue book

Bellevue sits in a mid-range mean band on this extract: about $391 from $96,131,734 divided by 245,666. The pair is a city-field average, not a ranking of political intensity.

High means can come from a few large lines. Low means can come from many modest lines. This packet has no top-line list, so neither story can be proven here.

A Bellevue total of $96,131,734 does not absorb Seattle, Kirkland, or Redmond. Those names are other city strings when filers typed them. State WA stays on the citation so BELLEVUE, WA is not merged with a same-named place elsewhere. The 245,666 lines and the mean near $391 describe this key only.

Do not stretch $96,131,734 past FEC.gov

This packet has no unique-donor count, no employer roll-up, and no party split. Anything in that list, if quoted as a fact about Bellevue, is not from this extract.

Cycle windows on the live hub may be rebuilt. This prose will not silently rewrite $96,131,734 after you load the page.

Keep Seattle, Kirkland, and Redmond off the Bellevue citation unless the receipt actually stored those cities. $96,131,734 is the BELLEVUE, WA string alone. 245,666 itemized rows and about $391 per row are the shape of that string, not of the metro map.

What a careful Bellevue sentence includes

Keep 245,666 as a contribution-line total. Researchers who need persons must match names on the city hub rather than treating the line count as a headcount.

The overlay target for this copy is the Bellevue city hub. The guide URL is a standalone citation page that points back to that hub.

Bellevue’s $96,131,734 on 245,666 lines is the Washington city key BELLEVUE, WA, mean near $391. Seattle is a different string. Kirkland, Redmond, and Mercer Island are other keys. King County geography orients; it does not create an Eastside roll-up. Bellevue, Nebraska would be a different state key — always include WA. Washington state-office campaigns are omitted. The 245,666-line count is itemized federal rows, not unique people. Tech-corridor geography is not an FEC employer table. Named receipts on the Bellevue hub are where employer may appear. Cite $96,131,734 and 245,666 together from FEC.gov via LobbyVault.

Questions

How much is itemized from contributor city Bellevue?

FEC.gov itemized receipts listing contributor city BELLEVUE, WA total $96,131,734 across 245,666 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 a census of people who live in Bellevue. Unitemized gifts sit outside it.

What does the Bellevue contribution count mean?

LobbyVault counts 245,666 itemized contributions for BELLEVUE, WA. That is a line count, not a headcount of unique people. Repeat gifts, redesignations, and memo entries can add rows without adding new donors. This packet does not publish a unique-donor figure, so 245,666 should not be quoted as a population. The matching dollar total on the same extract is $96,131,734.

Can committee addresses appear in the Bellevue city total?

No. The city is the contributor-city value on the FEC itemization. Filers typed BELLEVUE with state WA. Office addresses and mail that list Bellevue can be part of $96,131,734 when that is the city string on the receipt. LobbyVault does not recode the field into a residential-only book. The 245,666-line count follows the same rule.

Are Bellevue numbers from FEC.gov?

The numbers come from FEC.gov itemized contribution aggregates indexed on LobbyVault: $96,131,734 and 245,666 lines for BELLEVUE, 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 $391 is arithmetic from those two packet facts.