Channel
FUNNY888 Official 💚
@official_funny888
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,738subscribers
-156 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001689888588 |
|---|---|
| Type | Channel |
| Username | @official_funny888 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/official_funny888 |
Topic
Gambling & betting — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 03:05 | 4,738 | -12 |
| 22 Oct 2026, 03:16 | 4,750 | -19 |
| 15 Oct 2026, 12:49 | 4,769 | -12 |
| 12 Oct 2026, 22:56 | 4,781 | -8 |
| 6 Oct 2026, 05:58 | 4,789 | -18 |
| 29 Sept 2026, 01:18 | 4,807 | -22 |
| 19 Sept 2026, 13:38 | 4,829 | -12 |
| 15 Sept 2026, 08:59 | 4,841 | -17 |
| 12 Sept 2026, 00:59 | 4,858 | -7 |
| 7 Sept 2026, 21:42 | 4,865 | +9 |
| 2 Sept 2026, 18:02 | 4,856 | -8 |
| 1 Sept 2026, 23:05 | 4,864 | no change |
| 30 Aug 2026, 15:38 | 4,864 | +2 |
| 27 Aug 2026, 19:14 | 4,862 | -3 |
| 25 Aug 2026, 04:08 | 4,865 | -9 |
| 21 Aug 2026, 15:57 | 4,874 | -8 |
| 18 Aug 2026, 04:12 | 4,882 | -13 |
| 14 Aug 2026, 20:13 | 4,895 | -4 |
| 11 Aug 2026, 17:18 | 4,899 | +7 |
| 8 Aug 2026, 22:27 | 4,892 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@ballmunn · 23,060
Telegram ranks this channel #13 of 45 here — alongside 44 others — read 19 September 2026
@KC9999A9 · 27,899
Telegram ranks this channel #13 of 57 here — alongside 56 others — read 7 September 2026
@Jun88TH · 278,875
Telegram ranks this channel #13 of 68 here — alongside 67 others — read 4 September 2026
@huc999 · 23,530
Telegram ranks this channel #63 of 73 here — alongside 72 others — read 18 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“FUNNY888 Official 💚” (@official_funny888), 4,738 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/official_funny888.
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.