Telegram RegisterThe public register of Telegram
Telegram profile photo for Yan PayShark Blog

Channel

Yan PayShark Blog

@yan_ps

On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

4,790subscribers

+23 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002432477034
TypeChannel
Username@yan_ps
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/yan_ps

Topic

Giveaways & airdrops — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4,7554,8124,783.57 August 2026 — 4,767 subscribers8 August 2026 — 4,761 subscribers11 August 2026 — 4,760 subscribers14 August 2026 — 4,755 subscribers17 August 2026 — 4,774 subscribers21 August 2026 — 4,781 subscribers24 August 2026 — 4,796 subscribers27 August 2026 — 4,791 subscribers30 August 2026 — 4,790 subscribers2 September 2026 — 4,792 subscribers7 September 2026 — 4,812 subscribers12 September 2026 — 4,803 subscribers15 September 2026 — 4,790 subscribers4,7907 August 202615 September 2026
13 measurements spanning 39 days, net +23. 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 4,746–4,821 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 15:384,790-13
12 Sept 2026, 02:164,803-9
7 Sept 2026, 16:164,812+20
2 Sept 2026, 12:154,792+2
30 Aug 2026, 13:564,790-1
27 Aug 2026, 16:334,791-5
24 Aug 2026, 19:044,796+15
21 Aug 2026, 03:594,781+7
17 Aug 2026, 20:454,774+19
14 Aug 2026, 20:164,755-5
11 Aug 2026, 18:324,760-1
8 Aug 2026, 07:434,761-6
7 Aug 2026, 15:024,767first reading

Engagement

17 posts held, back to 25 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 6 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 17 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
6s
Average length
6s

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.

Recent posts

5 Aug 2026, 15:39 UTC76 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

🎉 Все призы успешно доставлены победителям! Мы выполнили все свои обещания - каждый победитель уже получил свой заслуженный приз. 📦 Спасибо всем, кто принимал участие, поддерживал проект и был частью этого события. Совсем скоро вас ждут новые активности, ещё более интересные механики и ещё больше возможностей выиграть ценные награды. 📸 Делимся фотографиями и видео от наших победителей. Спасибо за доверие и участие

25 Jul 2026, 14:23 UTC205 viewsread 12 August 2026
Forwarded from @TradeSharkNet

@boomer56 тоже отгадывает слово и забирает подарок: самый мощный майнер BitFarm! Поздравляем🎁

25 Jul 2026, 14:21 UTC199 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

@PayShark_Al_Capone забирает самый мощный майнер BitFarm! Поздравляем👑

25 Jul 2026, 14:16 UTC185 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

Photo, posted without a caption

25 Jul 2026, 14:09 UTC151 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

Photo, posted without a caption

25 Jul 2026, 14:04 UTC131 viewsread 12 August 2026
Forwarded from @TradeSharkNet

ЗАХОДИМ ОТГАДЫВАТЬ СЛОВА И ПОЛУЧАТЬ ПРИЗЫ🎁 👉🏻 ТЫК

25 Jul 2026, 14:00 UTC128 viewsread 12 August 2026
Forwarded from @TradeSharkNet

▶️ СТАРТ! 🔴 ОТГАДАТЬ СЛОВО - https://tradeshark.net/blackbox/

25 Jul 2026, 13:58 UTC125 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

🎁 BLACK BOX ВОЗВРАЩАЕТСЯ! - через 3 минуты старт! Сегодня в 17:00 по МСК мы снова открываем Black Box. 🦈 Внутри уже подготовлены новые призы, неожиданные сюрпризы и очередная серия загадок, которые предстоит разгадать всему сообществу. Что вас ждет сегодня: 🎁 Дорогие реальные призы 💰 Денежные награды 🎮 Техника и эксклюзивные подарки ❤️ Редкие бонусы экосистемы TradeShark 🎉 И, конечно, несколько сюрпризов, о котор

25 Jul 2026, 12:36 UTC75 viewsread 12 August 2026
Photo

🦈 Пользовательские токены уже в сети TradeShark! Создавайте собственные токены, покупайте перспективные проекты других участников и зарабатывайте на их росте. Каждый пользователь может запустить свой токен, собрать вокруг него комьюнити и попасть в раздел Trending, где самые успешные проекты получают дополнительное внимание. 📈 Уже сейчас некоторые пользовательские токены показывают впечатляющий рост и привлекают н

25 Jul 2026, 12:36 UTC761 viewsread 12 August 2026
Photo

🦈 Пользовательские токены уже в сети TradeShark! Создавайте собственные токены, покупайте перспективные проекты других участников и зарабатывайте на их росте. Каждый пользователь может запустить свой токен, собрать вокруг него комьюнити и попасть в раздел Trending, где самые успешные проекты получают дополнительное внимание. 📈 Уже сейчас некоторые пользовательские токены показывают впечатляющий рост и привлекают н

25 Jul 2026, 10:19 UTC98 viewsread 12 August 2026
Forwarded from @TradeSharkNetPhoto

🦈 +11X уже сделано. Один из пользовательских токенов, созданный нашим коллегой Баунсом, уже показал рост в 11 раза. 🚀 Если давно хотели попробовать пользовательские токены в экосистеме TradeShark - можете обратить внимание. ⚠️ Важно: это не финансовая рекомендация и не призыв к покупке. Любые инвестиции связаны с высоким риском. Если решите зайти - делайте это исключительно на свой страх и риск, предварительно из

25 Jul 2026, 09:56 UTC61 viewsread 12 August 2026
Forwarded from @TradeSharkNet

‼️ НАПОМИНАЕМ ЗА КОНКУРС

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

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Yan PayShark Blog” (@yan_ps), 4,790 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/yan_ps.

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.