Telegram RegisterThe public register of Telegram
Telegram profile photo for Beta Info Deutsch

Channel

Beta Info Deutsch

@betainfoger

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

59subscribers

+0 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001396512470
TypeChannel
Username@betainfoger
DescriptionInformationen zu Betaversionen von Telegram für alle Plattformen an einem Ort Chat: t.me/+X10bA-5L4xxlZjIy Hauptkanal: @tginfoger Englischer Kanal: @betainfoen Kontakt mit uns: @infowritebot Alle Tginfo Kanäle: @tginfoall Unterstützung: donate.tginfo.me
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/betainfoger

Growth

595 August 2026 — 59 subscribers10 August 2026 — 59 subscribers5 August 202610 August 2026
2 measurements spanning 4 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 58–60 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 05:4559no change
5 Aug 2026, 22:0659first reading

Engagement

20 posts held, back to 16 November 2025the 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 31 December 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
195
Videos
35
Links
441

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.

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 2 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 16 November 2025 to 31 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

31 Dec 2025, 03:58 UTC78 views2 reactionsread 10 August 2026
File

Telegram Beta Android 12.3.0 (6372) Änderungsprotokoll: • switch theme button • your info with phone, username, birthday in account settings • scroll optimization in dialogs list • send button animations, fix attach button with paid message price send button • fix ?direct link • profile buttons width fixes • fix preserving scroll position after switching language of chat translation, fix showing progress on translat

👍2

30 Dec 2025, 15:12 UTC69 viewsread 10 August 2026
File

Telegram Beta Android 12.3.0 (6368) Änderungsprotokoll: • fix top padding in settings, tg://settings fix, add account button fix • attach button at the top (conflicted with checkmark on outgoing messages), move it when entering inline bots • fix attach button in stories, fix back in stories and stories recorder • predictive back slides always right • crash fixes, minor fixes #Android #Apk

30 Dec 2025, 04:37 UTC53 views1 reactionsread 10 August 2026
File

Telegram Beta Android 12.3.0 (6365) Änderungsprotokoll: • Redesign: Das Seitenmenü wurde durch eine schwebende untere Tab-Leiste ersetzt. #Android #Apk

👍1

9 Dec 2025, 12:52 UTC59 viewsread 10 August 2026
File

Telegram Beta Android 12.2.11 (6342) Änderungsprotokoll: • fix back in photo viewer, and no back in android 13 • fix "disable animations" setting on folder with links (bugs.telegram.org/c/56605) • animated emojis from story edit/draft saves fix (bugs.telegram.org/c/55517) • some action layout fixes (bugs.telegram.org/c/57481, bugs.telegram.org/c/55277) • fix schedule repeat period when forwarding (bugs.telegram.org/

5 Dec 2025, 13:42 UTC51 viewsread 10 August 2026
File

Telegram Beta Android 12.2.10 (6340) Änderungsprotokoll: • predictive back support • fix album height with caption in reported issue #Android #Apk

5 Dec 2025, 06:12 UTC40 viewsread 10 August 2026
File

Telegram Beta Android 12.2.9 (6338) Änderungsprotokoll: • optimizations to profile animation in cpu implementation • fix log out in change number page #Android #Apk

3 Dec 2025, 19:36 UTC41 viewsread 10 August 2026
File

Telegram Beta Android 12.2.8 (6336) Änderungsprotokoll: • fixes #Android #Apk

2 Dec 2025, 22:13 UTC41 viewsread 10 August 2026
File

Telegram Beta Android 12.2.8 (6334) Änderungsprotokoll: – keine Details – #Android #Apk

27 Nov 2025, 19:02 UTC45 viewsread 10 August 2026
File

Telegram Beta Android 12.2.7 (6323) Änderungsprotokoll: • scroll position when chat open #Android #Apk

25 Nov 2025, 12:40 UTC48 viewsread 10 August 2026
File

Telegram Beta Android 12.2.6 (6319) Änderungsprotokoll: • fixed connecting issue • emoji status in chats list fix #Android #Apk

24 Nov 2025, 13:39 UTC46 viewsread 10 August 2026
File

Telegram Beta Android 12.2.5 (6317) Änderungsprotokoll: • glass fixes #Android #Apk

24 Nov 2025, 08:55 UTC42 viewsread 10 August 2026
File

Telegram Beta Android 12.2.5 (6316) Änderungsprotokoll: • photo animation optimization in profile screen • wallpaper fix for Android 9 • support predictive back for keyboard #Android #Apk

Showing the 12 most recent of 20 posts we hold for @betainfoger. 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 — 529,538 of 1,480,975entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 5 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.

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

“Beta Info Deutsch” (@betainfoger), 59 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/betainfoger.

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.