Channel
@im_j0kullse
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
139subscribers
+7 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001708802435 |
|---|---|
| Type | Channel |
| Username | @im_j0kullse |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/im_j0kullse |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 02:42 | 139 | +4 |
| 9 Sept 2026, 17:18 | 135 | +4 |
| 17 Aug 2026, 20:25 | 131 | -1 |
| 10 Aug 2026, 22:48 | 132 | no change |
| 10 Aug 2026, 04:30 | 132 | first reading |
7 posts held, back to 6 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 7 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
288 reactions across 7 posts, in 31 distinct kinds. The most used accounts for 8.33% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5283158194711980464 | 24 | 8.33% | |
| custom 5370828437252512737 | 17 | 5.90% | |
| custom 5388783655407597812 | 16 | 5.56% | |
| custom 5406863178506214811 | 16 | 5.56% | |
| custom 5792073340675954633 | 14 | 4.86% | |
| custom 5262496631764311741 | 13 | 4.51% | |
| custom 5287750859076156669 | 13 | 4.51% | |
| custom 5370647722208568436 | 13 | 4.51% | |
| custom 6179113575525651001 | 13 | 4.51% | |
| custom 5238084067718612816 | 12 | 4.17% | |
| custom 5269696779363836748 | 12 | 4.17% | |
| custom 5399995714778446143 | 12 | 4.17% | |
| custom 5275969403005993451 | 11 | 3.82% | |
| custom 5370743177856720717 | 11 | 3.82% | |
| custom 5900073596163724279 | 11 | 3.82% | |
| custom 5249184354860552061 | 10 | 3.47% | |
| custom 5382360652075521953 | 10 | 3.47% | |
| custom 5289685179202285561 | 9 | 3.13% | |
| custom 5276488149155991714 | 8 | 2.78% | |
| custom 6179339894532346010 | 7 | 2.43% | |
| 11 further kinds | 36 | 12.5% |
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 7 of the 7 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 288 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 6 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.
if you gonna ride don’t ride the white horse 🎶 на таком вайбе сегодня, наконец примерила жанчика пока не прям фулловый ковбойский прикид, не хватает разных аксессуаров • если вдруг кто-то хочет сигну, отпишитесь до 21:30, сделаю 😏
custom 528775085907615666913custom 523808406771861281612custom 524918435486055206110custom 53843690560925394314custom 52381265191753674143
Signed аннушка джокýлсе
📍Босоногая тропа щебень, гравий, шишки, навозные опилки - эти и другие покрытия ждали нас на протяжении 3,6 км но не весь материал чередовался, из-за чего дорожка казалось слегка однообразной полотенце - особый мастхэв, иначе отмыть зудящие ноги ледяной водой крайне сложно необычные ощущения, было очень увлекательно. дендрарий красивый, а жара не испортила впечатления. мои плоские стопы в приятном шоке 🥰 #review
custom 539999571477844614312custom 590007359616372427911custom 53823606520755219538custom 54743658094028613473
Signed аннушка джокýлсе
а я уже вернулась домой 🫶
custom 52896851792022855619custom 52831581947119804648custom 53887836554075978127custom 53777001787676605836custom 57919902373537447611
Signed аннушка джокýлсе
в пн отсняли школьных аруэни в стилевом переходе у меня пока так и не вышло съездить в минск, так что катя с подругой решили примчать утренним рейсом на один день, за что им большое спасибо. так приятно было наконец увидеться вживую ❤️ нащелкали много кадров и отлично провели время. в общем, интересный получился экспириенс и по совместительству мой первый парный проф фотосет ! #bts
custom 540686317850621481116custom 617911357552565100113custom 526969677936383674812custom 61793398945323460107custom 58619435465247332472
Signed аннушка джокýлсе
ура, наконец приехала на расчилловку к бабушке и остальным родственникам 💕 постараюсь запостить сюда кадры из поездки, а еще совсем скоро будет крутой косплей коллаб по аот 😉
custom 528315819471198046416custom 526249663176431174113custom 53887836554075978129custom 51886834612542041454custom 53100251521786914202
Signed аннушка джокýлсе
💡💡💡💡 💡💡💡💡💡 ➿➿➿➿➿➿➿➿➿➿ 🌟 𝙄𝙣 𝙩𝙝𝙚 𝙝𝙤𝙡𝙡𝙤𝙬 𝙤𝙛 𝙩𝙝𝙚 𝙜𝙧𝙚𝙖𝙩 𝙩𝙧𝙚𝙚 𝙩𝙝𝙖𝙩 𝙨𝙖𝙬 𝙚𝙫𝙚𝙧𝙮𝙩𝙝𝙞𝙣𝙜 𝙒𝙝𝙖𝙩 𝙙𝙤 𝙮𝙤𝙪 𝙪𝙣𝙙𝙚𝙧𝙨𝙩𝙖𝙣𝙙 ? ✦・。. 🤩🤩🤩 🤩🤩 🤩🤩 ✨️✨️✨️| Ph ➿➿➿➿➿ 🌟 #cosplay
custom 537082843725251273717custom 579207334067595463314custom 537064772220856843613custom 537074317785672071711custom 53709027401867348633
Signed аннушка джокýлсе
вот и прошел мой 2-й эпик 👍 он не был таким ярким, как предыдущий, но в этом есть своя фишка, тем более после перерыва в первый день наделали контента с эреном. второй день тоже был чилловый, гуляла в компании стэна и кайла! приятно, что пара человек узнала персонажа, тк фандом уже лет 5 холодный 😔 пофоткалась с другими косплеерами, удалось словить почти всех своих бро! именно на этом фесте за счет его масштаба соби…
custom 527596940300599345111custom 52764881491559917148custom 54452143545364246956custom 53777775010638858362custom 53823606520755219532
Signed аннушка джокýлсе
Showing the 7 most recent of 7 posts we hold for @im_j0kullse. 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“hear me, subjects of Ymir” (@im_j0kullse), 139 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/im_j0kullse.
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.