10 Jul 2022, 11:41 UTC52 viewsread 22 August 2026
.
Channel
OutOfOrder
@RaidSumBot_News
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
—subscribers
Register entry
| Telegram ID | -1001348855577 |
|---|---|
| Type | Channel |
| Username | @RaidSumBot_News |
| Created | Between 1 March 2018 and 7 May 2019— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 0 |
| On Telegram | t.me/RaidSumBot_News |
Growth
Growth history is still building. We hold no measurements for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
Engagement
20 posts held, back to 7 May 2019 — 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 pageof 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 20 posts for this entry, the most recent from 10 July 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 22 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.
Recent posts
10 Jul 2022, 11:00 UTCviews —
Channel photo removed
10 Jul 2022, 11:00 UTCviews —
Channel name was changed to «OutOfOrder»
2 Dec 2021, 14:14 UTC≈6,280 viewsread 22 August 2026
‼️ Achtung: Aktuell ist der RaidSumBot leider aufgrund einer technischen Störung offline ‼️
24 Jun 2021, 12:33 UTC773 viewsread 22 August 2026
⚠️ Wartung ⚠️ Morgen zwischen 14:00 - 14:30 führt mein Provider Wartungsarbeiten an einem der Server durch, dadurch wird der RSB in der Zeit offline sein. ⚠️ Wartung ⚠️
20 Jun 2021, 09:28 UTC731 viewsread 22 August 2026
Sorry hatte gerade ein Problem mit der Datenbank, musste den Server hart ersetzen, deshalb wurde der RSB gekillt und lässt eine alte Zusammenfassung im Kanal hängen, die neue sollte jetzt gleich wieder in den Kanälen ankommen. 🙈
11 May 2021, 07:58 UTC664 viewsread 22 August 2026
So nach ungeplanter Downtime fährt der Bot gerade wieder hoch, die "letzte" Nachricht vom Bot müsst ihr leider einmal manuell aufräumen, die Infos sind leider mit der vollen Festplatte auf dem Server untergegangen 🙈
19 Apr 2021, 07:43 UTC668 viewsread 22 August 2026
Muss den Bot mal eben neustarten, sollte gleich wieder da sein
19 Feb 2021, 10:58 UTC672 viewsread 22 August 2026
Sorry wurde von der Arbeit aufgehalten, Bot fährt jetzt wieder hoch, sollte gleich wieder überall da sein 😊
19 Feb 2021, 10:17 UTC592 viewsread 22 August 2026
Muss mal eben den Bot durchstarten, sollte in ca. 10-15 Minuten wieder da sein...
16 Oct 2020, 11:22 UTC653 viewsread 22 August 2026
So Server ist wieder oben, Bot kurbelt gerade wieder an...
16 Oct 2020, 11:14 UTC610 viewsread 22 August 2026
Moin, werd gleich mal eben den Bot kurz durchstarten müssen, sollte nicht allzulange dauern...
Showing the 12 most recent of 20 posts we hold for @RaidSumBot_News. 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.
Citation-graph rank
Citation-graph rank — 700,515 of 1,620,455entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
Named by 2 registered channels — 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. This entry holds no subscriber measurement yet, so the line below cites the entry itself.
“OutOfOrder” (@RaidSumBot_News). Telegram Register, tgregister.com/channel/RaidSumBot_News.
No subscriber measurement is held for this entry yet, so there is no history to download — a download that asserted zero readings would be a false statement, not an empty one.