Supergroup
ForkLog Community
@forklogcommunity
On this record: Topic · Previous handles · Growth · Engagement · Cite this entry
2,286members
+155 since we began measuring on 6 August 2026
294 online right now
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001397526471 |
|---|---|
| Type | Supergroup |
| Username | @forklogcommunity |
| Created | Between 1 August 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/forklogcommunity |
Topic
Crypto & trading — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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.
Previous handles
Recorded in 2019 as “ForkLog Community Board” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Members | Change |
|---|---|---|
| 12 Oct 2026, 15:46 | 2,286 | -3 |
| 5 Oct 2026, 21:20 | 2,289 | +4 |
| 28 Sept 2026, 04:41 | 2,285 | +8 |
| 18 Sept 2026, 23:58 | 2,277 | +8 |
| 18 Sept 2026, 00:41 | 2,269 | no change |
| 14 Sept 2026, 11:41 | 2,269 | +5 |
| 10 Sept 2026, 14:18 | 2,264 | +14 |
| 5 Sept 2026, 09:59 | 2,250 | +28 |
| 1 Sept 2026, 04:24 | 2,222 | +21 |
| 29 Aug 2026, 10:34 | 2,201 | -3 |
| 26 Aug 2026, 07:19 | 2,204 | +5 |
| 23 Aug 2026, 03:19 | 2,199 | +5 |
| 19 Aug 2026, 11:46 | 2,194 | +14 |
| 16 Aug 2026, 07:18 | 2,180 | +20 |
| 13 Aug 2026, 00:49 | 2,160 | +18 |
| 10 Aug 2026, 05:11 | 2,142 | +11 |
| 6 Aug 2026, 20:28 | 2,131 | 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.
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.
“ForkLog Community” (@forklogcommunity), 2,286 members as measured 12 October 2026. Telegram Register, tgregister.com/channel/forklogcommunity.
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.