Channel
🩸 BLOOD TRIBE OHIO 🩸
@bloodtribeohio
On this record: Topic · Growth · Engagement · Cite this entry
1,432subscribers
-46 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 | -1001910294769 |
|---|---|
| Type | Channel |
| Username | @bloodtribeohio |
| Created | 11 March 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 29 September 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/bloodtribeohio |
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 29 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 12 Oct 2026, 15:57 | 1,432 | -5 |
| 5 Oct 2026, 20:40 | 1,437 | -8 |
| 29 Sept 2026, 02:42 | 1,445 | no change |
| 28 Sept 2026, 14:59 | 1,445 | -1 |
| 18 Sept 2026, 17:38 | 1,446 | -4 |
| 14 Sept 2026, 09:40 | 1,450 | -1 |
| 10 Sept 2026, 09:40 | 1,451 | -2 |
| 4 Sept 2026, 23:17 | 1,453 | +1 |
| 1 Sept 2026, 02:08 | 1,452 | -4 |
| 28 Aug 2026, 16:24 | 1,456 | -1 |
| 25 Aug 2026, 17:32 | 1,457 | -3 |
| 22 Aug 2026, 21:09 | 1,460 | -1 |
| 19 Aug 2026, 04:47 | 1,461 | -5 |
| 16 Aug 2026, 05:58 | 1,466 | -2 |
| 12 Aug 2026, 22:26 | 1,468 | -7 |
| 9 Aug 2026, 15:11 | 1,475 | -3 |
| 6 Aug 2026, 09:59 | 1,478 | 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.
“🩸 BLOOD TRIBE OHIO 🩸” (@bloodtribeohio), 1,432 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/bloodtribeohio.
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.