Telegram RegisterThe public register of Telegram
Telegram profile photo for Holdap

Channel

Holdap

@holdap

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

269subscribers

+8 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001324198424
TypeChannel
Username@holdap
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/holdap

Growth

2612692656 August 2026 — 261 subscribers7 August 2026 — 261 subscribers14 August 2026 — 262 subscribers21 August 2026 — 268 subscribers28 August 2026 — 269 subscribers6 August 202628 August 2026
5 measurements spanning 22 days, net +8. 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 260–270 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 18:33269+1
21 Aug 2026, 13:57268+6
14 Aug 2026, 14:07262+1
7 Aug 2026, 01:03261no change
6 Aug 2026, 19:50261first reading

Engagement

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

Reaction mix

273 reactions across 11 posts, in 15 distinct kinds. The most used accounts for 16.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥4416.1%
custom 52764235227831064594115.0%
3713.6%
custom 5366407485680789065259.16%
custom 5276331735037021626238.42%
custom 5269298120499406873228.06%
💯228.06%
custom 5265031731915796998196.96%
🔥155.49%
custom 5343557473687053463114.03%
👀62.20%
custom 543810929751282565131.10%
custom 533679688592550477920.733%
custom 546752938540376236820.733%
custom 533724327046651083010.366%

Custom emoji. 10 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 11 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 273 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 20 June 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, 06:58 UTC85 views27 reactionsread 7 August 2026
Photo

И еще новые реакцииии в тгканале к выходу нового сингла 🖤 Пссс уже совсем скоро...✝️ Хочешь узнать какой смысл я вкладываю в цвет обложки? 🤪 Если да то, оставь реакции под этим постом и комент, и через пару дней я расскажу тебе о синем цвете🍎

custom 527642352278310645911custom 53435574736870534637👀4❤‍🔥1🔥1custom 53367968859255047791custom 54381092975128256511custom 54675293854037623681

5 Aug 2026, 05:32 UTC91 views20 reactionsread 7 August 2026

👁️DRY TOBACCO SOON👁️

❤‍🔥6💯5custom 52763317350370216263custom 53435574736870534632custom 54381092975128256512👀1custom 53372432704665108301

5 Aug 2026, 05:31 UTC89 views24 reactionsread 7 August 2026
Video message

Video message, posted without a caption

10custom 52764235227831064595custom 52650317319157969984❤‍🔥1👀1custom 53367968859255047791custom 53664074856807890651custom 54675293854037623681

18 Jul 2026, 16:46 UTC238 views41 reactionsread 7 August 2026
Video

URAL MUSIC NIGHT / 26

custom 527642352278310645916❤‍🔥7custom 52650317319157969986custom 53664074856807890654custom 52692981204994068733custom 527633173503702162621💯1

15 Jul 2026, 10:39 UTC275 views19 reactionsread 7 August 2026
Photo

Выступаю в эту пятницу в Ставников Бар, приходи буду ждать🧛💀🧛

custom 52692981204994068736🔥4custom 536640748568078906531❤‍🔥1💯1custom 52650317319157969981custom 52763317350370216261

8 Jul 2026, 17:07 UTC299 views20 reactionsread 7 August 2026
Photo

Скоро новый трек и концерт 🎟 Купить билеты 🎟

🔥74custom 53664074856807890653💯2custom 52650317319157969981custom 52692981204994068731custom 52763317350370216261custom 52764235227831064591

5 Jul 2026, 15:19 UTC305 views17 reactionsread 7 August 2026
Photo

ЗАХОДИ НА СТРИМ💯💯💯

💯5custom 52692981204994068734custom 53664074856807890653custom 52764235227831064592❤‍🔥1🔥1custom 52650317319157969981

4 Jul 2026, 17:29 UTC182 views15 reactionsread 7 August 2026
Forwarded from @moneyhillssPhoto

11 ИЮЛЯ В БАРЕ СИНДРОМ ДЛЯ ТЕБЯ БУДУТ ВЫСТУПАТЬ: • КОЛЯ ХОЛДАП • SCOUNDREL • MOONI • YUNGGIBA • HOLYKIR • МОНОНОКА • RMNVA • FROOFYU • ПЛАКСА • BLU • SHUMKA + SPECIAL GUESTS 🦷 Приходи зарядится вайбами уральского андеграунда, яркими фразами и мощными рифами! На мероприятии будет живая музыка от лайв-бенда "Друнк" (Миша и Саша) 🤩 Не упусти это лето! Приходи к нам на ивент, будет жарко 🔥☝🏿 🎟 КУПИТЬ БИЛЕТ 🎟 До вст

7❤‍🔥2custom 52764235227831064592custom 52650317319157969981custom 52692981204994068731custom 53435574736870534631custom 53664074856807890651

30 Jun 2026, 11:27 UTC244 views21 reactionsread 7 August 2026

Бустаните кнопочку, сделаю вам нишевые реакции🧛🧛🧛 https://t.me/boost/holdap

💯6custom 52692981204994068735custom 52650317319157969983custom 52763317350370216262custom 527642352278310645921❤‍🔥1custom 53664074856807890651

30 Jun 2026, 11:26 UTC243 views33 reactionsread 7 August 2026
Photo

Еще фотки с UMN🌵 Видео уже монтируем☝🏿🏁 photo by

❤‍🔥10custom 5276331735037021626107custom 52692981204994068732custom 53664074856807890652💯1custom 52650317319157969981

20 Jun 2026, 17:35 UTC336 views36 reactionsread 7 August 2026
Photo

Первые снимки с Ural Music Night 💯🫀🔪 pic

❤‍🔥14custom 536640748568078906576custom 52763317350370216264custom 52764235227831064592💯1🔥1custom 52650317319157969981

Showing the 11 most recent of 11 posts we hold for @holdap. 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

Named by 8 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

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

“Holdap” (@holdap), 269 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/holdap.

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.