Telegram RegisterThe public register of Telegram
Telegram profile photo for Plebs

Channel

Plebs

@plebs_again

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

1,847subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001248452034
TypeChannel
Username@plebs_again
Created12 June 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/plebs_again

Growth

1,8471,8561,851.56 August 2026 — 1,851 subscribers6 August 2026 — 1,851 subscribers7 August 2026 — 1,853 subscribers9 August 2026 — 1,851 subscribers13 August 2026 — 1,854 subscribers17 August 2026 — 1,853 subscribers20 August 2026 — 1,856 subscribers24 August 2026 — 1,853 subscribers27 August 2026 — 1,855 subscribers30 August 2026 — 1,853 subscribers2 September 2026 — 1,849 subscribers7 September 2026 — 1,847 subscribers6 August 20267 September 2026
12 measurements spanning 32 days, net -4. 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 1,846–1,857 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 09:391,847-2
2 Sept 2026, 12:431,849-4
30 Aug 2026, 22:531,853-2
27 Aug 2026, 22:251,855+2
24 Aug 2026, 16:151,853-3
20 Aug 2026, 19:441,856+3
17 Aug 2026, 09:351,853-1
13 Aug 2026, 07:051,854+3
9 Aug 2026, 23:341,851-2
7 Aug 2026, 04:501,853+2
6 Aug 2026, 11:311,851no change
6 Aug 2026, 11:041,851first reading

Engagement

31 posts held, back to 4 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 31 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
6m 51s
Average length
2m 17s

Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

467 reactions across 29 posts, in 2 distinct kinds. The most used accounts for 63.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 518838281354348877729863.8%
custom 535973493186393537316936.2%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 29 of the 31 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 467 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 31 most recent posts we hold, published 4 August 2026 to 7 August 2026, 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

7 Aug 2026, 10:43 UTC507 views22 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 518838281354348877719custom 53597349318639353733

Signed Иниго Монтойя

7 Aug 2026, 06:38 UTC420 views7 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 51883828135434887776custom 53597349318639353731

Signed Иниго Монтойя

7 Aug 2026, 06:09 UTC394 views12 reactionsread 7 August 2026
Forwarded from @polariss_aPhoto

Photo, posted without a caption

custom 51883828135434887779custom 53597349318639353733

Signed Иниго Монтойя

7 Aug 2026, 06:00 UTC458 views21 reactionsread 7 August 2026
Photo

доброе утро

custom 518838281354348877714custom 53597349318639353737

Signed Иниго Монтойя

6 Aug 2026, 15:35 UTC547 views6 reactionsread 7 August 2026
Video

я давно хотел запостить это видео, надеюсь сделать плебс кулинарным каналом

custom 51883828135434887776

Signed Иниго Монтойя

6 Aug 2026, 15:29 UTC495 views13 reactionsread 7 August 2026
Photo

ладно

custom 518838281354348877713

Signed Иниго Монтойя

6 Aug 2026, 15:21 UTC480 views8 reactionsread 7 August 2026
Forwarded from @ash_tree_lanePhoto

Photo, posted without a caption

custom 53597349318639353738

Signed Иниго Монтойя

6 Aug 2026, 15:02 UTC478 views14 reactionsread 7 August 2026
Forwarded from @baronglistPhoto

Photo, posted without a caption

custom 53597349318639353739custom 51883828135434887775

Signed Иниго Монтойя

6 Aug 2026, 14:57 UTC504 views13 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 535973493186393537311custom 51883828135434887772

Signed Иниго Монтойя

6 Aug 2026, 14:56 UTC378 views20 reactionsread 7 August 2026
Forwarded from @NORMANDIEmkPhoto

Photo, posted without a caption

custom 535973493186393537320

Signed Иниго Монтойя

6 Aug 2026, 14:56 UTC421 views16 reactionsread 7 August 2026
Forwarded from @siniekabachkiPhoto

Photo, posted without a caption

custom 535973493186393537316

Signed Иниго Монтойя

6 Aug 2026, 10:13 UTC≈1,350 views39 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 535973493186393537330custom 51883828135434887779

Signed bela lugoshi

Showing the 12 most recent of 31 posts we hold for @plebs_again. 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.

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

“Plebs” (@plebs_again), 1,847 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/plebs_again.

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.