Sponsored link

Quick answer

Zee Wiki builds on two kinds of ground: official Roblox surfaces — the game page for place 85002796582175, the ZHD Entertainment group, and Roblox’s public data APIs — which decide what the game is, and named community sources — code trackers, clip sites, directories — which are used to map what the surrounding Zee Hood family claims, always with their own place bindings attached. Every fact on this site names its source and carries a checked date; September 2026 API snapshots are archived in the site’s research record so an older observation can be compared against a newer one without rewriting history. The register below lists each source, what it is allowed to support, and when it was last inspected — including the source types that simply do not exist for this game.

The source register

Source register, checked November 3, 2026. “Supports” is the only use each source is put to on this site.
SourceTypeSupportsChecked
Official Zee game pageOfficial (Roblox)Game identity, official description, ten-day rule, platform list, maturity label, live countersSeptember 8, 2026; place-identity binding re-checked November 3, 2026 (description and rule surfaces are signed-in views)
Universe resolver APIOfficial API (Roblox)Place-to-universe binding (85002796582175 → 10765344821)November 3, 2026
Roblox Games API — universe metadataOfficial API (Roblox)Created and updated dates, 35-player server cap, visits, favorites, full description snapshotSnapshots September 8–9, 2026; on November 3, 2026 the anonymous read returned a content-restricted placeholder
Roblox Groups API — group 637891611Official API (Roblox)Creator identity, owner (Coillaid), member counts, community tierSeptember 9, 2026; re-checked November 3, 2026
Group games API — public experiencesOfficial API (Roblox)The ZHD place family list and its changes over timeNovember 3, 2026
Roblox Thumbnails APIOfficial media (Roblox)Provenance of the official cover art (ZEE HOOD artwork record)September 8, 2026
Roblox Badges APIOfficial API (Roblox)Badge inventory for this universe (returned empty)September 8, 2026
Roblox Den (Zee Hood) — code listCommunity code trackerSame-name family codes and the place its own game button targets (115667308362952)August 25, 2026; place binding re-checked November 3, 2026
Roblox Den (ZEE) — code listCommunity code trackerSame-name family codes and the place its own game button targets (119474995301163)August 25, 2026; place binding re-checked November 3, 2026
GameRant — code listCommunity code trackerSame-name family codes and the place its own game button targets (130702048271596)Article published August 20, 2025 (by Artur Novichenko); game link re-checked November 3, 2026; place binding re-checked November 3, 2026
GameRant — "Roblox Zee Hood codes"Games mediaFamily-level code claims (BUBU, MUSIC, KINGPIN, Katana!, NEW!) and redemption descriptionArticle published August 20, 2025; game-link binding re-checked November 3, 2026
Medal.tv — Zee clip hubCommunity clipsEvidence of current-game community footageNovember 3, 2026
Disboard directoryCommunity directoryExistence of third-party "Zee Hood crew" server listingsNovember 3, 2026
YouTube — verron Zee Hood gameplay videosCommunity videoFamily-level history; 2025 footage of older same-name gamesSeptember 8, 2026
zeehood.orgIndependent fan siteObserved as a fan hub with Discord-based perks; carries no creator affiliation proofSeptember 8, 2026

Source types this game does not have

Absences are facts too, and for a game this young they explain most of the confusion in search results. As of November 3, 2026: there is no official Trello board linked from any creator surface (checked September 8, 2026 and again October 3); there is no creator-verified Discord — third-party servers exist, none carries creator provenance; there is no official or Fandom wiki dedicated to this place, which makes this independent fan site the closest thing; there is no official patch-notes channel, so the update page tracks Roblox metadata instead of inventing changelogs; and the creator shows no official YouTube or X account in the checked surfaces. Community code trackers cover the family, but none covers this place — a gap the codes page documents source by source. When one of these appears, the affected page grows a new entry with its source and date; until then the gap is stated, not filled.

How a fact earns its place

Four rules govern every page here. Official first: where the game’s own description speaks, it wins — the ten-day rule, the platform list and the creator identity all come from Roblox surfaces, and APIs are used to timestamp and archive them. Place number before name: a claim applies to this game only if its source binds to place 85002796582175; the number after /games/ in a Roblox URL outranks logos, titles and publish dates. Checked is not live: every date marks an inspection — counters move, announcements age, and a snapshot from September 8, 2026 is presented as just that. Conflicts stay visible: when sources disagree, both claims are shown with attribution, because averaging a 500K and a 1M cash reward into “750K” would manufacture a fact nobody published.

The same discipline sets the limits. The account-age calculator is arithmetic from the published rule, labeled an estimate because the server owns the final rounding; the growth numbers on the homepage are point-in-time snapshots, not trends; and statements about what this site could not establish appear once, where they apply, instead of padding every page. A claim that cannot name a source does not go up — rumor strings fail this test and stay off the site, including code strings that circulate in comments without ever gaining a place binding.

What we never import

The Zee Hood name carries years of family history — 2025 gameplay videos, weapon lists, code tables, map guides. None of it enters this site without a place binding, because the family spans at least five Roblox places by the November 3, 2026 count and imported “facts” would describe games the reader is not playing. That is also why the wiki’s reference table can be short: it holds only what place 85002796582175 has actually published or its APIs have actually recorded. If you maintain another fan resource, the same two-question test works everywhere: which place is this about, and when was it checked? Sources that cannot answer belong in the citation, not the claim — and if you find us breaking that rule, the contact page is the fastest way to get it fixed.

Useful answers

Does "checked" mean the information is live?

No. A checked date records when a source was inspected and what it showed at that moment. Stat counters and timestamps move constantly; the date lets you judge how much time has passed rather than trusting an undated claim.

Why do community trackers get listed if their codes do not apply here?

Because knowing what they cover is evidence too: each tracker's own game button binds it to a specific place, and documenting those bindings (none match place 85002796582175) is how the codes page can say no list applies — with receipts instead of assertions.

What happens when two sources disagree?

Both claims get shown, attributed — like the 1M-versus-500K cash conflict between Roblox Den and GameRant. Pages never average conflicting numbers into a fake consensus, and the identity check (place number) outranks any amount.

Can I challenge a source or a fact?

Yes — the contact page takes corrections with the page URL and a public supporting source. A correction that checks out is applied with a fresh checked date, the same way any other update is.