Channel
F8 Audit and Assurance
@f8auditandassurance
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
10,190subscribers
+186 since we began measuring on 8 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001768310818 |
|---|---|
| Type | Channel |
| Username | @f8auditandassurance |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/f8auditandassurance |
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 24 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 |
|---|---|---|
| 24 Oct 2026, 23:26 | 10,190 | +2 |
| 24 Oct 2026, 02:46 | 10,188 | +7 |
| 22 Oct 2026, 23:19 | 10,181 | +11 |
| 21 Oct 2026, 22:08 | 10,170 | +6 |
| 20 Oct 2026, 17:45 | 10,164 | -13 |
| 19 Oct 2026, 17:57 | 10,177 | -12 |
| 17 Oct 2026, 13:54 | 10,189 | +9 |
| 16 Oct 2026, 13:08 | 10,180 | +3 |
| 15 Oct 2026, 11:01 | 10,177 | +7 |
| 14 Oct 2026, 09:51 | 10,170 | +3 |
| 12 Oct 2026, 18:57 | 10,167 | +9 |
| 8 Oct 2026, 04:41 | 10,158 | +20 |
| 3 Oct 2026, 15:38 | 10,138 | +36 |
| 24 Sept 2026, 21:17 | 10,102 | +32 |
| 18 Sept 2026, 14:38 | 10,070 | -1 |
| 16 Sept 2026, 05:40 | 10,071 | +17 |
| 14 Sept 2026, 15:01 | 10,054 | +25 |
| 12 Sept 2026, 22:02 | 10,029 | +20 |
| 11 Sept 2026, 00:38 | 10,009 | +5 |
| 8 Sept 2026, 21:01 | 10,004 | 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.
@accaglobal_a · 32,276
Telegram ranks this channel #3 of 80 here — alongside 79 others — read 8 September 2026
@accastudents · 39,623
Telegram ranks this channel #8 of 63 here — alongside 62 others — read 8 September 2026
@listeningforeveryone · 24,770
Telegram ranks this channel #28 of 59 here — alongside 58 others — read 25 September 2026
@CFAL1_FREE · 36,239
Telegram ranks this channel #45 of 62 here — alongside 61 others — read 8 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 24 October 2026 — this entry's latest reading, not the date you are reading this.
“F8 Audit and Assurance” (@f8auditandassurance), 10,190 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/f8auditandassurance.
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.