Telegram RegisterThe public register of Telegram
Telegram profile photo for Raids Refrath

Channel

Raids Refrath

@RaidsRefrath

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

50subscribers

+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-1001323154370
TypeChannel
Username@RaidsRefrath
DescriptionRaids, Votes & Quests für Refrath Mit Benutzung des Kanals erkennst du verlinkten Disclaimer + Datenschutzerklärung von MyPGoBot an + bestätigst, mind. 1️⃣6️⃣ Jahre alt zu sein! Disclaimer: www.mypgobot.de/de/datenschutz/
Created14 September 2018measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live22 August 2026
Measurements held2
On Telegramt.me/RaidsRefrath

Growth

507 August 2026 — 50 subscribers10 August 2026 — 50 subscribers7 August 202610 August 2026
2 measurements spanning 3 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 49–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 11:1650no change
7 Aug 2026, 23:1150first reading

Engagement

10 posts held, back to 14 September 2018the 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.

ERR · 30 days
35.0%
avg views ÷ 50 subscribers
Avg views / post
17.5
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 10 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held10 (14 September 20184 August 2026)
Views total35
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 11:16 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Links
5

Lifetime counters from Telegram’s own channel header, read 10 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

4 Aug 2026, 18:52 UTC10 viewsread 10 August 2026

Raidstunde . Mittwoch, 05.08.2026 18:30 (UTC+02) Spielplatz Buchweizenweg Apple MapsiCal Google Kalender 👍 Ja (3) @WildcardCR @Phan99 ★ @YohYou3 👎 Nein (3) @Gisator1 @tomttom00 @Wuffels1974

Signed Julian

29 Jul 2026, 08:46 UTC25 viewsread 10 August 2026

Raidstunde . Mittwoch, 29.07.2026 18:30 (UTC+02) Spielplatz Buchweizenweg Apple MapsiCal Google Kalender 👍 Ja (3) @WildcardCR @tech_nik51 ★ @YohYou3 👎 Nein (3) @Gisator1 @Wuffels1974 @Phan99

Signed Julian

31 Jan 2024, 17:57 UTCviews —

Raids Refrath pinned «Mit überwiegenden Mehrheit wurde auf der letzten Raidstunde angeregt, zukünftig wie folgt zu verfahren: Wenn es nur darum geht, 2 Raidpässe rauszuhauen, starten wir erst um 18:30 Uhr. Bei Raids, wo sich auch grüne Pässe lohnen, bleibt es bei 18:00 Uhr oder…»

31 Jan 2024, 17:57 UTC≈1,980 viewsread 10 August 2026

Mit überwiegenden Mehrheit wurde auf der letzten Raidstunde angeregt, zukünftig wie folgt zu verfahren: Wenn es nur darum geht, 2 Raidpässe rauszuhauen, starten wir erst um 18:30 Uhr. Bei Raids, wo sich auch grüne Pässe lohnen, bleibt es bei 18:00 Uhr oder anderen individuellen Zeiten

Signed Dirk B. (WildcardCR, CGN)🇩🇪

3 Dec 2020, 20:05 UTC≈5,320 viewsread 10 August 2026

Update bei der Raid-Darstellung! Nachdem die automatische Raidmeldung nun wieder stabil läuft, quellen die ständigen Popups der angezeigten Raids aus mittlerweile 28 Arenen über. Daher wird die Raidanzeige zukünftig auf die Infobox alleine beschränkt. Eine Aktivierung der Raidanmeldung erfolgt dann durch Anklicken der Arena. Evtl. etwas hochscrollen, danach läuft alles wie bisher. Großer Vorteil: Wer sich über Raids

Signed Dirk B. (WildcardCR, CGN)🇩🇪

18 Oct 2019, 19:21 UTC≈3,210 viewsread 10 August 2026

Tauschgruppe für Ex-Raidpässe und mehr in Refrath: ReTrEx https://t.me/joinchat/Cn6U9U9QTfo2sjlIKpkxOQ

Signed Dirk B. (WildcardCR, CGN)🇩🇪

3 Sept 2019, 11:33 UTC≈2,540 viewsread 10 August 2026

Zusätzliche Events wie z. B. "Staub farmen beim Rossmann" oder "Community Day im Wald" können übrigens von jedermann über den @eeventbot erstellt werden. Teilt diese dann an @WildcardCR, damit diese - sofern sie angemessen sind - den Weg in diesen Kanal finden können

Signed Dirk B. (WildcardCR, CGN)🇩🇪

9 Apr 2019, 20:01 UTC≈2,640 viewsread 10 August 2026

Hallo Trainer und Willkommen! Hier gibt es Informationen so besonderen (raren) Forschungsaufgaben und Raids in Refrath - daher der Name RaRe 😉 Die Kanalinformationen stammen vom @MyPGoBot und dem @bookofquestsbot. Wer die Bots vollständig nutzen will, dem seien die Disclaimer der jeweiligen Bots empfohlen. Einfach anschreiben, starten, lesen, bestätigen und individuell nutzen 😉 Dieser Kanal bietet jeweils nur eine A

Signed Dirk B. (WildcardCR, CGN)🇩🇪

Showing the 10 most recent of 10 posts we hold for @RaidsRefrath. 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 — 1,433,120 of 1,605,487entries 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 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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“Raids Refrath” (@RaidsRefrath), 50 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/RaidsRefrath.

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.