Telegram RegisterThe public register of Telegram
Telegram profile photo for ruslan.black

Channel

ruslan.black

@ruslanblack69

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

50subscribers

+3 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002418076300
TypeChannel
Username@ruslanblack69
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/ruslanblack69

Growth

475048.510 August 2026 — 47 subscribers10 August 2026 — 47 subscribers17 August 2026 — 50 subscribers24 August 2026 — 49 subscribers19 September 2026 — 50 subscribers10 August 202619 September 2026
5 measurements spanning 40 days, net +3. 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 47–50 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 05:4050+1
24 Aug 2026, 13:0349-1
17 Aug 2026, 16:1650+3
10 Aug 2026, 13:3447no change
10 Aug 2026, 06:0147first reading

Engagement

20 posts held, back to 23 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 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
57s
Average length
57s

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

14 reactions across 11 posts, in 2 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5321280354496051699857.1%
custom 5319259400584591747642.9%

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 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 14 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 23 July 2026 to 10 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

10 Aug 2026, 09:56 UTC5 viewsread 10 August 2026

ахах, двух недель не прошло в этот раз

7 Aug 2026, 22:03 UTC15 viewsread 10 August 2026

починил. теперь у меня нет проблем с лимитами. аж дышать легче стало. нахуй режим!

6 Aug 2026, 19:08 UTC21 viewsread 10 August 2026

я вангую рэперы и овнеры команд из инстаграма скоро будут флексить кластерами NVIDIA DGX, кто быстрее? надо успеть купить, чтоб не завидовать.

6 Aug 2026, 07:41 UTC25 views1 reactionsread 10 August 2026

ранее был уверен, что я никогда не найду причину спать по режиму. серьёзней всего были ситуации с начальниками, что решительно коррелировали качество моей работы с приходом в 8-9 утра, на том обычно и прощались. появился Claude Code, со сбросом лимитов раз в 5 часов. я как-то случайно научился спать по несколько часов, но 2-3 раза в день, встаю и сплю очень хорошо, чувствую себя замечательно. и заметил это вообще с

custom 53212803544960516991

6 Aug 2026, 07:37 UTC24 views1 reactionsread 10 August 2026

согласен жить по режиму, только если этот режим - пятичасовые сбросы лимитов Клода

custom 53192594005845917471

6 Aug 2026, 07:33 UTC26 viewsread 10 August 2026

как же всё замечательно сложилось, что я могу каждое утро спускаться на тайский массажик, всего лишь часик поохуевать от боли, зато потом весь день филяй-филяй 🙏🏻

4 Aug 2026, 16:44 UTC32 views1 reactionsread 10 August 2026

уф блин, знаете есть такие дни, когда зашел в кс, и всё попадаешь, и всё летит, и в голову? сегодня не такой день.

custom 53212803544960516991

4 Aug 2026, 09:27 UTC36 views3 reactionsread 10 August 2026
Photo

не унывай

custom 53192594005845917473

3 Aug 2026, 10:20 UTC33 viewsread 10 August 2026

https://github.com/banochkin/ide-server-prune vs code заебал срать в систему при ssh подключении! неделю билдили, чтоб всё ок работало на linux и macos. в сети хватает разнообразных костылей для чистки системы, но все с нюансами. ну мы свои сделали.

2 Aug 2026, 10:33 UTC34 viewsread 10 August 2026

ебать как приятно смотреть полгода челика на ютубе, что просто делает перевод на русский одного там обозревателя разных интересных тем, а потом как вспомнить, что я же английский знаю, и могу смотреть в оригинале. не задавайте вопросов.

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

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.

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

“ruslan.black” (@ruslanblack69), 50 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/ruslanblack69.

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.