https://vm.tiktok.com/ZNRmFQA7t/

Channel
BritishComedy
@BritishComedy
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001391205923 |
|---|---|
| Type | Channel |
| Username | @BritishComedy |
| Created | Between 1 June 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/BritishComedy |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:02 | 1 | no change |
| 7 Aug 2026, 19:13 | 1 | first reading |
Engagement
12 posts held, back to 25 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 12 posts for this entry, the most recent from 4 March 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 758
- Videos
- 52
- Links
- 143
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 51s
- Average length
- 51s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
File, posted without a caption
https://vm.tiktok.com/ZNRaTFKmU/
https://www.facebook.com/share/v/14cU7RoKCHt/
File, posted without a caption
File, posted without a caption
“Ring final circuit continuity not confirmed – R1 open circuit recorded during end-to-end testing
Yes — you’re absolutely right 👍 Using “fault finding” can confuse customers. A more professional EICR approach is to state the defect clearly and then recommend remedial works, not “investigation”. Here is the reworded single recommendation paragraph, no mention of fault finding, clearly explaining the C2 condition in technical but professional terms: Recommendations: Remedial works are required to Circuit 5, where…
All good — here’s the updated single recommendation paragraph, still compact, with C2 items first, then C3, and the fire detection added in clean British wording: Recommendations: Urgent fault-finding is required on Circuit 5 due to an R1 open circuit and high Zs readings (C2). The lighting installation supplied by a single 6A RCBO should be divided so each lighting circuit is provided with its own protective device…
No problem at all 👍 — this is ultra-condensed EICR box wording, the kind inspectors actually use when space is really tight. Everything you said is still covered, just stripped right back. Condition of the installation: Supply cut-out sealed; earthing satisfactory. No main isolator to consumer unit (C3). Plastic consumer unit, not fire-rated, with no visible cable entry protection (C3). No SPD fitted (C3). Circuit 2…
Photo, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 12 posts we hold for @BritishComedy. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“BritishComedy” (@BritishComedy), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/BritishComedy.
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.