Telegram RegisterThe public register of Telegram
Telegram profile photo for JuliK.CR

Channel

JuliK.CR

@julik_cr

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

291subscribers

+19 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-1003985734691
TypeChannel
Username@julik_cr
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/julik_cr

Growth

2702962837 August 2026 — 272 subscribers7 August 2026 — 270 subscribers21 August 2026 — 282 subscribers29 August 2026 — 296 subscribers5 September 2026 — 293 subscribers13 September 2026 — 291 subscribers2917 August 202613 September 2026
6 measurements spanning 37 days, net +19. 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 266–300 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 01:36291-2
5 Sept 2026, 18:15293-3
29 Aug 2026, 15:42296+14
21 Aug 2026, 22:13282+12
7 Aug 2026, 20:44270-2
7 Aug 2026, 02:03272first reading

Engagement

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

Reaction mix

88 reactions across 9 posts, in 6 distinct kinds. The most used accounts for 47.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53958476740186746834247.7%
custom 53977171916782427542427.3%
custom 539557626215033912277.95%
custom 519285749945102175955.68%
custom 538447869801767058755.68%
custom 539538076812392745155.68%

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

Measured over the 10 most recent posts we hold, published 6 August 2026 to 6 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

6 Aug 2026, 15:37 UTC50 views13 reactionsread 7 August 2026
Photo

Друзья, товарищи) Ситуация стандартная, конкурс прошел, пошли отписки. Всем базам база. Но хочу предупредить сразу, что возможности вернуться нет, если выходите - попадаете в черный список. Конкурсов будет много, если вам нравится тут находиться и всё устраивает, замечательно. Если нет, то потом пожалуйста не обижайтесь 💋 Всем хорошего вечера и участвуйте в конкурсе на наряд для гг выше 🤩

custom 53955762621503391227custom 53977171916782427546

6 Aug 2026, 13:06 UTC53 views13 reactionsread 7 August 2026
Photo

Кто тут кот, а кто мышка? 😍 #адриан #рожденная_солнцем #julik_cr

custom 53977171916782427546custom 53953807681239274514custom 53958476740186746832custom 51928574994510217591

6 Aug 2026, 12:51 UTC64 views1 reactionsread 7 August 2026

дубль 2, жду ваши юиды в личные сообщения канала в течении суток

custom 53958476740186746831

6 Aug 2026, 12:50 UTC66 views1 reactionsread 7 August 2026

Выбор дополнительных победителей (в количестве 2): 🏆 Победители: 1. Ayan (@Hesenliayanlala) 2. Daria (@bad_wolf_corp) ✔️Проверить результаты

custom 53958476740186746831

6 Aug 2026, 11:11 UTC69 views3 reactionsread 7 August 2026
Photo

Милые, еще раз. Это не стандартный гардероб в который вы привыкли играть. Мне нужно реальное платье. Например, пишите гг. Эва и кидаете фото платья

custom 53977171916782427543

6 Aug 2026, 10:29 UTCviews —

JuliK.CR pinned «Думаю, все знакомы с «Гардеробом»: дают тему, участники подбирают образ для главной героини, а потом начинается голосование. Но что, если немного поменять правила? 🙄 Под этим постом вы выбираете главную героиню и отправляете вечернее платье, которое хотели…»

6 Aug 2026, 10:28 UTC67 views9 reactionsread 7 August 2026

Думаю, все знакомы с «Гардеробом»: дают тему, участники подбирают образ для главной героини, а потом начинается голосование. Но что, если немного поменять правила? 🙄 Под этим постом вы выбираете главную героиню и отправляете вечернее платье, которое хотели бы на ней увидеть. Желательно на белом фоне - такого добра на Pinterest навалом 😃 Дальше в игру вступаю я: делаю обработку с выбранной вами ГГ в вашем платье, соби

custom 53958476740186746839

6 Aug 2026, 10:06 UTC65 views20 reactionsread 7 August 2026
Photo

Хотите такую подборку по своему любимому фавориту? Напиши в комментарии 🔽 #руди #тенисентфора2 #julik_cr

custom 539584767401867468312custom 51928574994510217594custom 53977171916782427544

6 Aug 2026, 09:06 UTC65 views11 reactionsread 7 August 2026
Photo

Мне опять скучно на работе, так что развлекаюсь как могу Новая история от Маришки, мы пока что не видели гг, но немного пофантазируем, как бы она могла выглядеть. Видела такую идею у Женечки, когда она представляла как бы могла выглядеть Рен из Рожденной Солнцем. Ждете новые истории? #рождённый_тенью #julik_cr

custom 53958476740186746838custom 53977171916782427542custom 53953807681239274511

6 Aug 2026, 08:10 UTC71 views17 reactionsread 7 August 2026
Photo

Замечательная ᏒᎥᎷᎥᏗᏒ𐐆Ꮥ передала эстафету «Сельский тайм-аут» от канала Дневник кицунэ|Кр 🐷❤️ Так что любуемся деревенским вайбом 😂 Передаю всем желающим и дорогой psiheyasbox Суть эстафеты: Вам нужно поместить героев визуальной новеллы в полный деревенский антураж. Это может быть один или несколько персонажей. Может быть романтика, сельский экшн с участием кур, профиль горячего тракториста или дойка коровы. Все на ва

custom 53958476740186746839custom 53844786980176705875custom 53977171916782427543

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

Mentions

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

“JuliK.CR” (@julik_cr), 291 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/julik_cr.

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.