Channel
Souls In Ruin / Blood & Steel / ONCE UPON A BROKEN HEART
@OuAbHeart
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,153subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002063786930 |
|---|---|
| Type | Channel |
| Username | @OuAbHeart |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 19 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/OuAbHeart |
Topic
Literature — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 16:10 | 2,153 | +2 |
| 1 Nov 2026, 21:46 | 2,151 | +2 |
| 30 Oct 2026, 00:39 | 2,149 | -1 |
| 27 Oct 2026, 11:11 | 2,150 | -1 |
| 24 Oct 2026, 10:34 | 2,151 | -4 |
| 21 Oct 2026, 15:30 | 2,155 | -7 |
| 18 Oct 2026, 09:59 | 2,162 | -4 |
| 14 Oct 2026, 23:35 | 2,166 | -2 |
| 11 Oct 2026, 14:19 | 2,168 | +8 |
| 5 Oct 2026, 13:18 | 2,160 | -4 |
| 27 Sept 2026, 13:40 | 2,164 | -3 |
| 19 Sept 2026, 01:14 | 2,167 | no change |
| 15 Sept 2026, 12:20 | 2,167 | +2 |
| 11 Sept 2026, 20:37 | 2,165 | -10 |
| 7 Sept 2026, 05:59 | 2,175 | +8 |
| 2 Sept 2026, 05:05 | 2,167 | +5 |
| 30 Aug 2026, 13:38 | 2,162 | -1 |
| 27 Aug 2026, 19:04 | 2,163 | -2 |
| 24 Aug 2026, 09:13 | 2,165 | +12 |
| 20 Aug 2026, 11:24 | 2,153 | 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.
@Romaanico · 42,662
Telegram ranks this channel #13 of 61 here — alongside 60 others — read 6 September 2026
@BOOKESTUNN · 32,780
Telegram ranks this channel #38 of 59 here — alongside 58 others — read 6 September 2026
@shahregoftegoo · 19,865
Telegram ranks this channel #60 of 65 here — alongside 64 others — read 1 October 2026
@romanmamnoeee · 64,662
Telegram ranks this channel #66 of 67 here — alongside 66 others — read 30 August 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Souls In Ruin / Blood & Steel / ONCE UPON A BROKEN HEART” (@OuAbHeart), 2,153 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/OuAbHeart.
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.