eeu.cny — County Catalog

Status: ✅ Cracked · 400 KB · NOT_COMPRESSED

A real sub-national administrative catalog — one level below eeu.stt's "state" table (regions/cantons — cracked in a later session), one level above eeu.cty's cities/localities.

Field names corrected: this page originally called the first two fields index/region_id, guessed before eeu.mod (the disc's own schema dictionary) was found. The real names are countyID/stateID, and this file is genuinely the schema's "county" table (not a "region" table itself, as first guessed).

Record format

94-byte header (record count 2,326 read straight off its own header field), then exactly 2,326 fixed 176-byte records — validated at full scale: every record parses cleanly, zero exceptions.

uint16 LE  county_id    -- eeu.mod's real name: countyID
uint16 LE  state_id     -- eeu.mod's real name: stateID, see below
bytes[26]               -- always zero (see below)
bytes[36]  name         -- NUL-padded
uint8      timeinfo_id  -- eeu.mod's real name: timeinfoID, see below
bytes[109]              -- always zero (see below)

name — real administrative divisions

Confirmed directly, not just plausible-looking. The first 5 records alone are CHANIA, RETHYMNO, IRAKLEIO, LASITHI — the 4 real prefectures of Crete, Greece, in their real west-to-east geographic order — followed immediately by IMPERIA, a real Italian province in Liguria. Further records include:

• All 8 real provinces of Piedmont, Italy: TORINO, CUNEO, ASTI, ALESSANDRIA, BIELLA, VERCELLI, NOVARA, VERBANO-CUSIO-OSSOLA.
• Real districts of the Swiss canton Valais: MONTHEY, SAINT-MAURICE, MARTIGNY, ENTREMONT, CONTHEY, SION, HERENS, SIERRE, LEUK, VISP, BRIG.
• Real districts of Vaud: NYON, MORGES, LAUSANNE, AIGLE, ...
• Real districts of Fribourg: LA SARINE, LA GRUYÈRE, LA GLÂNE, SENSE, ...

state_id — a real foreign key into eeu.stt's "state" table

Not a country reference — eeu.cal/ eeu.cat's own country_id tops out at 34; this reaches 690. eeu.mod's schema confirms stateID is a real foreign key into eeu.stt (region/canton records with their own bounding box and county-id range).

Validated directly against real geography: every county with state_id=4 is a real Valais district; state_id=6 is Vaud; state_id=8 is Fribourg; state_id=3 groups Piedmont's 8 provinces; state_id=39 groups Liguria's (Imperia, Savona). 691 distinct values total — plausible for ~34 countries' real regional/cantonal subdivisions.

Confirmed directly in a later session, against eeu.stt's own real content (not just plausibility) — see eeu.stt — State/Region Catalog: this file's 691 distinct state_id values are the exact same set as eeu.stt's own 691 state_id values, and CHANIA→KRITI/Greece, IMPERIA→LIGURIA/Italy, and SION→WALLIS/Switzerland all resolve exactly right against eeu.stt's own content.

Not allocated in the file's own record order — the first-seen sequence (by increasing county_id) is 0, 39, 3, 1, 4, 2, 5, 6, ..., not 0, 1, 2, 3, ... — consistent with it being a real foreign key assigned by eeu.stt's own record order (confirmed).

timeinfo_id (byte 66) — a real foreign key into eeu.ti

Range 1–13, heavily skewed: 1 alone covers 1,674/2,326 (72%) of all records; 3 is next-most-common (398, 17%). Constant within 681/691 (98.6%) of state_id groups.

eeu.mod's schema names the field immediately after name in the real "county" table timeinfoID — a foreign key into eeu.ti's own "timeinfo" table (timezone, start year/month/day/hour, duration — plausibly a Daylight Saving Time rule definition). This fits the value shape well (most counties share a common "default" profile) and directly explains why this page's two originally-tested hypotheses both failed:

• A direct country reference — doesn't match eeu.cal/eeu.cat's numbering, and the same value recurs across clearly different countries.
• A count of that county's own child localities in eeu.cty — real sub-locality counts for 5 sample counties (15/6/35/8/31) don't relate to their own timeinfo_id values (3/3/3/1/1).

It isn't counting or naming the county at all — it's pointing at a shared, county-independent time-rule catalog.

Confirmed directly in a later session, against eeu.ti's own real content — see eeu.ti — Time-Info / DST Rule Table: the 2 timeinfo_id values with rich, detailed sub-schedule data in eeu.ti (1 and 3, each with 3 sub-records) are exactly this field's own 2 most common values (72% and 17% of all counties respectively) — an exact, non-coincidental correspondence.

The always-zero regions

The 26 bytes between state_id and name, and the 109 bytes after timeinfo_id, match the schema's own remaining "county" fields (zoneID, start_cityID, end_cityID, cover, a min_long/min_lat/ max_long/max_lat bounding box, alpha_cities, cityID) — all apparently unpopulated for every county on this disc, not incorrectly identified. Exact per-field byte boundaries weren't independently determined (every candidate field being zero makes the split unverifiable from this file's own content alone).

Practical use

Combine with eeu.cal/ eeu.cat and eeu.stt for a 4-level administrative hierarchy (country → state → county → city), and with eeu.cty for the city level itself.

Reader code

research/cny_reader.py — read_cny().