Channel
@RaidsLudwigslustUndNeustadtGlewe
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
36subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001202387522 |
|---|---|
| Type | Channel |
| Username | @RaidsLudwigslustUndNeustadtGlewe |
| Description | Chat und Support: https://t.me/joinchat/FZJ4_FbrBH1qyYlLzU_Rwg |
| Created | 22 March 2019 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/RaidsLudwigslustUndNeustadtGlewe |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 22:15 | 36 | no change |
| 7 Aug 2026, 23:11 | 36 | first reading |
11 posts held, back to 22 March 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 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 11 posts for this entry, the most recent from 5 December 2021. An engagement rate over an empty window would be a number about nothing.
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.
Raids Ludwigslust und Neustadt Glewe pinned «Der Raid-Kanal funktioniert wie folgt: 1⃣ Die Raids werden in einer Liste, der sogenannten Infobox, angezeigt. 2⃣ Möchte man einem Raid zusagen, dann bitte selbigen in der Liste antippen. Dies führt dazu, dass sich ein neues Fenster öffnet und welches…»
Der Raid-Kanal funktioniert wie folgt: 1⃣ Die Raids werden in einer Liste, der sogenannten Infobox, angezeigt. 2⃣ Möchte man einem Raid zusagen, dann bitte selbigen in der Liste antippen. Dies führt dazu, dass sich ein neues Fenster öffnet und welches bei einigen Browsern ggf. manuell geschlossen werden muss. 3⃣ Der Raid wird als Einzelnachricht in den Kanal geschickt. Bitte nur Raids in den Kanal holen, an denen…
Signed Admins
Bitte jeden der hier in der RAID Gruppe ist diesen allgemeinen Kanal bei zu treten dient um besser Verständigung der RAID Gruppe. Oder einfach auf den Button ( CHAT & SUPPORT) unten KLICKEN. Vielen Dank Pflichtangaben vom Botbetreiber: MyPGoBot-Newskanal: @MyPGoBot_News MyPGoBot-Spende: https://www.paypal.me/MyPGoBot
Signed Steffen Behnke
https://t.me/joinchat/GyEvgVbrBH2j8uhBb1iJzw
Signed Steffen Behnke
https://t.me/EnterRaidBot?start=aid=29491 Da auch solche Kanäle wie diese nicht an der Datenschutzerklärung vorbei kommen, gibt es jetzt oben einen Link dafür. Dort bitte einmal rauf gehen, unten auf Starten tippen und danach den Disclaimer bestätigen. Bei Fragen zu diesem Bot, falls der Scan mal nicht funktioniert, hilft euch auch folgende Anleitung: https://telegra.ph/EnterRaidBot-Raids-und-Raidbosse-melden-11-24
Signed Radulff
Damit einmalig bleibt, was einmalig ist (aktuellere Anleitung): https://telegra.ph/Telegram-Benutzername-festlegen-07-24
Signed Radulff
Location, posted without a caption
Signed Radulff
Exraids werden nun immer gelistet.
Signed RaidSumBot
/enter_raid
Signed Radulff
Nicht erlaubt im Channel! Bitte persönlichen Bot oder den EnterRaidBot verwenden! (Bei Drücken des Links werden die Einstellungen des Kanals bei der Ersteinrichtung des EnterRaidBots übernommen)
Signed MyPGoBot
Channel created
Showing the 11 most recent of 11 posts we hold for @RaidsLudwigslustUndNeustadtGlewe. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@RaidsLudwigslustUndNeustadtGlewe named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 Ludwigslust und Neustadt Glewe” (@RaidsLudwigslustUndNeustadtGlewe), 36 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/RaidsLudwigslustUndNeustadtGlewe.
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.