Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegram Tweets (DE)

Channel

Telegram Tweets (DE)

@de_telegram

On this record: Growth · Engagement · Posts · Citations · Cite this entry

37subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001275774418
TypeChannel
Username@de_telegram
CreatedBetween 1 April 2018 and 29 April 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/de_telegram

Growth

363736.56 August 2026 — 36 subscribers10 August 2026 — 36 subscribers14 August 2026 — 37 subscribers6 August 202614 August 2026
3 measurements spanning 8 days, net +1. 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 36–37 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 22:0437+1
10 Aug 2026, 22:1636no change
6 Aug 2026, 23:5236first reading

Engagement

20 posts held, back to 29 April 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.

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 29 April 2018. An engagement rate over an empty window would be a number about nothing.

Recent posts

29 Apr 2018, 13:34 UTC≈1,810 viewsread 10 August 2026

Should be up for most in Europe, see https://t.co/N4j3RaxwZe ^M — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,800 viewsread 10 August 2026

Hallo, Bot-API sollte nun wieder funktionieren. Klappt es bei euch wieder? ^M — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,790 viewsread 10 August 2026

The service is now restored for most of Europe, Africa, Russia and CIS, Iran and Middle East coming soon. Americas and SE Asia unaffected by the outage (the same outage also took offline the Amsterdam airport and ~18.000 households). — Telegram Messenger (@telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,740 viewsread 10 August 2026

Hey, wir arbeiten noch dran. Sorry für die Unannehmlichkeiten. — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,580 viewsread 10 August 2026

Hey, sorry für die Unannehmlichkeiten. Es sollte nun langsam wieder funktionieren. — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,360 viewsread 10 August 2026

Hey, sorry für die Unannehmlichkeiten. Es sollte nun langsam wieder funktionieren. — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC941 viewsread 10 August 2026

Our Eurocluster finally got the power back. All engineers are on deck working hard to restore the equipment after the outage. Telegram is coming back to the affected users in Europe, Middle East and the CIS. Please hang on! — Telegram Messenger (@telegram) April 29, 2018

29 Apr 2018, 11:59 UTC≈1,100 viewsread 10 August 2026

Hey, sorry für die Unannehmlichkeiten. Es sollte nun langsam wieder funktionieren. — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:59 UTC803 viewsread 10 August 2026

Hey there, we are currently experiencing some issues, but we are working hard to resolve these. Sorry for any inconvenience caused https://t.co/rNwy68whN4 — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:39 UTC739 viewsread 10 August 2026

Hey there, we are currently experiencing some issues, but we are working hard to resolve these. Sorry for any inconvenience caused https://t.co/rNwy68whN4 — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:39 UTC690 viewsread 10 August 2026

Hallo, tut uns sehr leid. Wir arbeiten dran! Sorry für die Unannehmlichkeiten https://t.co/rNwy68whN4 — Telegram auf Deutsch (@de_telegram) April 29, 2018

29 Apr 2018, 11:39 UTC657 viewsread 10 August 2026

Hallo, leider haben wir gerade in mehreren Regionen ein paar Probleme, aber wir arbeiten dran! Sorry für die Unannehmlichkeiten https://t.co/rNwy68whN4 — Telegram auf Deutsch (@de_telegram) April 29, 2018

Showing the 12 most recent of 20 posts we hold for @de_telegram. 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,290,005 of 1,481,217entries 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.

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.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“Telegram Tweets (DE)” (@de_telegram), 37 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/de_telegram.

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.