Telegram RegisterThe public register of Telegram
Telegram profile photo for π‚π—Žπ—Ήπ—½ΦΊπΌπŸ‡ͺπŸ‡Έ

Channel

π‚π—Žπ—Ήπ—½ΦΊπΌπŸ‡ͺπŸ‡Έ

@culpa_journ

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

10subscribers

-6 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003885882581
TypeChannel
Username@culpa_journ
Created26 July 2026 β€” measured β€” dated from the channel’s first post
First recorded11 August 2026
Last confirmed live4 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/culpa_journ

Topic

Other / unclassifiable β€” a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured β€” it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

10161311 August 2026 β€” 16 subscribers11 August 2026 β€” 16 subscribers20 August 2026 β€” 13 subscribers26 August 2026 β€” 12 subscribers4 September 2026 β€” 11 subscribers4 October 2026 β€” 10 subscribers11 August 20264 October 2026
6 measurements spanning 53 days, net -6. 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 9–17 and does not start at zero.
Measurement log β€” every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 00:5810-1
4 Sept 2026, 06:0111-1
26 Aug 2026, 21:3312-1
20 Aug 2026, 06:1613-3
11 Aug 2026, 22:1716no change
11 Aug 2026, 14:4816first reading

Engagement

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

What this channel posts

Video runtime
1m 40s
Average length
1m 40s

Measured directly from 1 video 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

70 reactions across 11 posts, in 9 distinct kinds. The most used accounts for 22.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
πŸ“1622.9%
⚑1420.0%
πŸ”₯1217.1%
πŸ’―710.0%
πŸŽƒ68.57%
πŸ’‹57.14%
πŸ†45.71%
❀34.29%
πŸ•Š34.29%

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 12 of the 19 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 70 reactions in total: the kind of figure the paragraph above means by β€œa reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 26 July 2026 to 5 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

5 Aug 2026, 19:04 UTC9 views5 reactionsread 11 August 2026
Photo

tomorrow??? loading...

⚑2πŸ“1πŸ’―1πŸ•Š1

28 Jul 2026, 10:40 UTC83 views6 reactionsread 11 August 2026
Video

πŸŽ€. πŸ”Ήπ΄Χ…πžˆ π˜ƒΔ±π—±π΄Χ…α¦… πŸ€©πŸŽ€ 🀩 зна𝝰ֺк𑄝ֺм𝗰тв𑄝ֺ 𝗰 н𝝰ֺми πŸŽ€ 🀍 β€’ βžΏβž–βžΏβœ¨βžΏβž–βžΏ β€’ 🀍 Π½π°ΦΊΠΏΠΈΡˆΠΈΡ‚π΄ Π² ΠΊπ‘„ΦΊΠΌΠΌπ΄Π½ΠΈπ°ΦΊΡ€ΠΈΡπ˜… к𝝰ֺк в𝝰ֺм н𝝰ֺш𝝴 𑄝ֺф𑄝ֺ𝗽Ϋͺмл𝝴ни𝝴

πŸ“3⚑1❀1πŸ”₯1

27 Jul 2026, 21:39 UTC26 views0 reactionsread 11 August 2026

ΠΆΠ΄ΠΈΡ‚Π΅ ΠΎΡ‚ нас ΠΏΠ΅Ρ€Π²ΠΎΠ΅ Π²ΠΈΠ΄Π΅ΠΎ!

27 Jul 2026, 21:36 UTC35 views7 reactionsread 11 August 2026
Photo

🍭 πŸŽ€ αͺΰ£ͺΦΈ 𝐏𝗿𑄝ֺ𝗳i𝗹e . . 2 πŸ«₯ !! 🀩 🀩🀩🀩🀩🀩🀩 β€œβ€ πŸŽ€ πŸŽ‡ π“”π˜ƒeɾყ sΧ…π˜ΦΊα¦…ΙΎαƒ§ h𐐼sΧ… ı𝘁ֺsΧ… α¦…πžˆn 𝗰ׅᦅnsΧ…eπ—Ύπ—Žen𝗰ׅesΧ… . πŸ™Œ πŸŽ€β˜„οΈπŸŽ€ππ°me ::πŸŽ€ 𝐌𝝰ֺΙ₯π˜ƒΙ₯ πŸŽ€ πŸŽ€πŸ€ β€’ ➿ βž– { ✨} βž–βžΏ β€’πŸ€ πŸ€πŸŽ€ β€˜β€™β€™ 𝐏𝗿o𝘁o𝘁y𝗽Ϋͺe:: 𝐂h𝝰ֺeᨰׁׅo𝗻Ϋͺ 🀩 y.o 11 πŸ’‹ . ⊹۫ .’’’ 𝐉𑄝oπž„π—Ώπ—»Ϋͺ𝝰ֺ𝗹iπ˜€π˜π˜€ who wi𝗹𝗹 𝗰o𝗻Ϋͺπ—Ύπž„e𝗿 π΄π˜ƒπ΄π—Ώyo𝗻Ϋͺ𝝴.. π–₯” 🀍🀍🀍🀍🀩🀩🀩🀍🀍🀍🀍

⚑3πŸ“2πŸŽƒ1πŸ”₯1

27 Jul 2026, 21:35 UTC37 views12 reactionsread 11 August 2026
Photo

🍭 πŸŽ€ αͺΰ£ͺΦΈ 𝐏𝗿𑄝ֺ𝗳i𝗹e . . 1 πŸ«₯ !! 🀩 🀩🀩🀩🀩🀩🀩 β€œβ€ πŸŽ€ πŸŽ‡ π“”π˜ƒeɾყ sΧ…π˜ΦΊα¦…ΙΎαƒ§ h𐐼sΧ… ı𝘁ֺsΧ… α¦…πžˆn 𝗰ׅᦅnsΧ…eπ—Ύπ—Žen𝗰ׅesΧ… . πŸ™Œ πŸŽ€β˜„οΈπŸŽ€ππ°me ::πŸŽ€ππ°ΦΊπ—Ώi𝗻Ϋͺπ΄πŸŽ€ πŸŽ€πŸ€ β€’ ➿ βž– { ✨} βž–βžΏ β€’ 🀍 πŸŽ€ πŸ€πŸŽ€ β€˜β€™β€™ 𝐏𝗿o𝘁o𝘁y𝗽Ϋͺe:: πŠπ°ΦΊπ˜‡πž„h𝝰ֺ 🀩 πŸŽ€ y.o 17 πŸ’‹ . ⊹۫ .’’’ 𝐉𑄝oπž„π—Ώπ—»Ϋͺ𝝰ֺ𝗹iπ˜€π˜π˜€ who wi𝗹𝗹 𝗰o𝗻Ϋͺπ—Ύπž„e𝗿 π΄π˜ƒπ΄π—Ώyo𝗻Ϋͺ𝝴.. π–₯” 🀍🀍🀍🀍🀩🀩🀩🀍🀍🀍🀍

⚑3πŸ“3❀2πŸ’‹2πŸ”₯2

27 Jul 2026, 21:00 UTC43 views7 reactionsread 11 August 2026

п𝗽Ϋͺ𑄝ֺф𝝰ֺйлы н𝝰ֺ 10 𝗽Ϋͺ𝝴𝝰ֺкций

πŸ“2πŸŽƒ2πŸ†2πŸ’―1

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

Mentions

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 4 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œπ‚π—Žπ—Ήπ—½ΦΊπΌπŸ‡ͺπŸ‡Έβ€ (@culpa_journ), 10 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/culpa_journ.

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.