Greater Bridgeport Planning Region, CT: 8 findings, 3 at a watch level and 5 noted
8 findings fired for Greater Bridgeport Planning Region, CT this run, against covered employment of 113,518 in 2026 Q1.
Rules version 1. Assembled 2026-10-19. Back to Greater Bridgeport Planning Region, CT.
8 findings #
watchGreater Bridgeport Planning Region, CT's covered employment is -1.1% against a year earlier, a watch level here: covered employment below the same quarter a year earlier (BLS QCEW over-the-year percent change, as published; not an official level). The previous published period is not in this table, so this is a standing level rather than a change.
Period 2026 Q1.Show the arithmetic
- test: jobs.yoy.emp = -1.1 < 0
BLS QCEW over-the-year percent change, as published; not an official level
watchGreater Bridgeport Planning Region, CT's covered employment of 113,518 scores 92 on the 0-to-100 scale across US counties but 38 across Connecticut counties, a gap of 54 points.
Period 2026 Q1.Show the arithmetic
- 54 = |92 across US counties - 38 across Connecticut counties|
position among the entities that published this metric this period; not an official level
watchGreater Bridgeport Planning Region, CT's average weekly wage of $1,566 scores 94 on the 0-to-100 scale across US counties but 63 across Connecticut counties, a gap of 32 points.
Period 2026 Q1.Show the arithmetic
- 32 = |94 across US counties - 63 across Connecticut counties|
position among the entities that published this metric this period; not an official level
noteGreater Bridgeport Planning Region, CT's average weekly wage was 1.2% higher than the same quarter a year earlier in 2026 Q1, on BLS QCEW's published over-the-year change.
Period 2026 Q1.Show the arithmetic
- +1.2 % = BLS QCEW over-the-year percent change for 2026 Q1, as published
- the newest QCEW file carries no year-earlier level, so no move from one level to another is printed
BLS QCEW over-the-year percent change, as published
noteGreater Bridgeport Planning Region, CT's covered employment was 1.1% lower than the same quarter a year earlier in 2026 Q1, on BLS QCEW's published over-the-year change.
Period 2026 Q1.Show the arithmetic
- -1.1 % = BLS QCEW over-the-year percent change for 2026 Q1, as published
- the newest QCEW file carries no year-earlier level, so no move from one level to another is printed
BLS QCEW over-the-year percent change, as published
noteGreater Bridgeport Planning Region, CT's average weekly wage of $1,566 ranks 188th of 3,221 US counties, against a median of $1,039.
Period 2026 Q1.Show the arithmetic
- 94 on the 0-to-100 scale across 3221 US counties that published jobs.avgWeeklyWage
position among the entities that published this metric this period; not an official level
noteGreater Bridgeport Planning Region, CT's covered employment of 113,518 ranks 274th of 3,221 US counties, against a median of 8,232.
Period 2026 Q1.Show the arithmetic
- 92 on the 0-to-100 scale across 3221 US counties that published jobs.emp
position among the entities that published this metric this period; not an official level
noteThe next Unemployment rate (BLS Employment Situation, monthly) covering Greater Bridgeport Planning Region, CT is due between 2026-10-30 and 2026-11-13, estimated from the publisher's past release pattern.
Show the arithmetic
- window = 2026-10-30 to 2026-11-13, estimated from the publisher's past release pattern
estimated from the publisher's past release pattern; not an announced date
Findings come from a fixed rule table and a fixed sentence per rule. There is no model in this path: the numbers are detected, ordered and worded by code, and every one of them prints the operation that produced it.
Next release #
BTS Border Crossing Entry Data (monthly), expected between 2026-10-10 and 2026-10-30.
The window is approximate: the publisher has not posted a date for this release, so it is inferred from the cadence of previous ones.
The same brief, narrowed #
A lens keeps the findings whose subject matches one reader's interest and hides the rest. Every lens brief points its canonical here.
Subscribe #
The same findings as a feed. Entry ids are content hashes with no clock in them, so an unchanged finding is never sent twice.