Telegram RegisterThe public register of Telegram
Telegram profile photo for Марксистский угол

Channel

Марксистский угол

@truemarxist

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

285subscribers

-13 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-1002499183452
TypeChannel
Username@truemarxist
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live14 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/truemarxist

Growth

285298291.57 August 2026 — 298 subscribers8 August 2026 — 297 subscribers8 August 2026 — 297 subscribers16 August 2026 — 294 subscribers22 August 2026 — 290 subscribers28 August 2026 — 289 subscribers6 September 2026 — 288 subscribers14 September 2026 — 285 subscribers7 August 202614 September 2026
8 measurements spanning 38 days, net -13. 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 283–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 14:00285-3
6 Sept 2026, 14:15288-1
28 Aug 2026, 20:14289-1
22 Aug 2026, 18:36290-4
16 Aug 2026, 08:54294-3
8 Aug 2026, 08:04297no change
8 Aug 2026, 01:03297-1
7 Aug 2026, 16:41298first reading

Engagement

20 posts held, back to 20 July 2026the 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

30 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5226457200406328352620.0%
😁620.0%
custom 5425041996953695971310.0%
👍310.0%
🤔310.0%
😭26.67%
custom 542727542719225583413.33%
13.33%
❤‍🔥13.33%
🌭13.33%
😢13.33%
🤝13.33%
🤡13.33%

Custom emoji. 3 of the rows above are 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 11 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 30 reactions 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 20 July 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, 19:09 UTC35 views2 reactionsread 8 August 2026

Смерть в нищите

👍1🤝1

Signed Владислав

7 Aug 2026, 19:08 UTC40 views2 reactionsread 8 August 2026
Photo

Photo, posted without a caption

❤‍🔥1custom 54272754271922558341

6 Aug 2026, 14:03 UTC53 views5 reactionsread 8 August 2026
Photo

Photo, posted without a caption

👍2😭2🌭1

Signed Владислав

28 Jul 2026, 19:14 UTC95 views6 reactionsread 8 August 2026
Photo

Photo, posted without a caption

😁6

Signed Владислав

27 Jul 2026, 07:52 UTC111 views7 reactionsread 8 August 2026
Photo

Photo, posted without a caption

custom 52264572004063283526🤡1

Signed Владислав

Showing the 12 most recent of 20 posts we hold for @truemarxist. 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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“Марксистский угол” (@truemarxist), 285 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/truemarxist.

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.