Telegram RegisterThe public register of Telegram
Telegram profile photo for MOBB DEEP

Channel

MOBB DEEP

@MobbDeepOfficial

Has discussion group

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,512subscribers

+25 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001134447804
TypeChannel
Username@MobbDeepOfficial
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live12 October 2026
Measurements held15
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/MobbDeepOfficial

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 27 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,4871,5251,5066 August 2026 — 1,487 subscribers9 August 2026 — 1,491 subscribers12 August 2026 — 1,496 subscribers15 August 2026 — 1,504 subscribers19 August 2026 — 1,510 subscribers22 August 2026 — 1,516 subscribers25 August 2026 — 1,521 subscribers31 August 2026 — 1,516 subscribers4 September 2026 — 1,525 subscribers9 September 2026 — 1,516 subscribers13 September 2026 — 1,514 subscribers17 September 2026 — 1,519 subscribers27 September 2026 — 1,518 subscribers27 September 2026 — 1,518 subscribers12 October 2026 — 1,512 subscribers1,5126 August 202612 October 2026
15 measurements spanning 67 days, net +25. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,481–1,531 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 04:001,512-6
27 Sept 2026, 17:051,518no change
27 Sept 2026, 12:361,518-1
17 Sept 2026, 23:361,519+5
13 Sept 2026, 11:401,514-2
9 Sept 2026, 09:211,516-9
4 Sept 2026, 09:211,525+9
31 Aug 2026, 16:471,516-5
25 Aug 2026, 16:041,521+5
22 Aug 2026, 21:371,516+6
19 Aug 2026, 04:551,510+6
15 Aug 2026, 20:271,504+8
12 Aug 2026, 00:521,496+5
9 Aug 2026, 10:341,491+4
6 Aug 2026, 04:111,487first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 October 2026 — this entry's latest reading, not the date you are reading this.

“MOBB DEEP” (@MobbDeepOfficial), 1,512 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/MobbDeepOfficial.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.