![Telegram profile photo for [𝗜𝗡𝗙𝗢] ᨦSᨵfִɬׁCᨵꭉִꫀִׄദ](https://cdn.tgregister.com/av/a3/a3b54fa1a6417035cc64202e14c652849bb847bee7be6ca1cbea5b632b81ff72.jpg)
Channel
@infosoftcore
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
1subscribers
-19 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003923735147 |
|---|---|
| Type | Channel |
| Username | @infosoftcore |
| Created | 8 May 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 18 October 2026 |
| On Telegram | t.me/infosoftcore |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 18 October 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Oct 2026, 19:20 | 1 | -19 |
| 11 Aug 2026, 16:16 | 20 | no change |
| 11 Aug 2026, 03:46 | 20 | first reading |
9 posts held, back to 8 May 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 9 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
386 reactions across 5 posts, in 7 distinct kinds. The most used accounts for 24.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422351638029437496 | 94 | 24.4% | |
| custom 5373059127301938286 | 71 | 18.4% | |
| custom 5373319561233868470 | 49 | 12.7% | |
| custom 5363913608625423939 | 44 | 11.4% | |
| custom 5373324616410375432 | 44 | 11.4% | |
| custom 5298586554757848241 | 43 | 11.1% | |
| custom 5251431198281972359 | 41 | 10.6% |
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 8 of the 9 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 386 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 8 May 2026 to 19 July 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @infosoftcore. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 9 most recent posts we hold for this entry, published 8 May 2026 to 19 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Sticker, posted without a caption
custom 537331956123386847011custom 537332461641037543210custom 53730591273019382868custom 54223516380294374966custom 52514311982819723595custom 52985865547578482415
˛ִִ ֺ ۣ ʾ.˛ִִ ֺ ۣ࿙ᮬֺ ⏜۫۫۫͜ᮬ︵ ꒰ַᮬ࡙۫۫ 🤍𐐫ֺ͜𐐫ֺ͜𝐤 𐐫ֺ͜f 𝇄ִ 𝐥𐐫ֺ͜𝐯̈ᤢᧉ꒱︵۫͜ᮬ۫۫⏜𝂅ִׄׄ 𓈒˛ִִ ֺ ۣ࿚ׄ ۣ ˛ִִ ֺ ۣ ︵۫͜ᮬ۫۫ ׁ ֺ ֺۣ ʾ࿙ᮬ🤩 :𐑺ֺ ֵׄ۫𝅄 ֺ𝆋 ㌞ִֺ⸼𝅄 ꒰ַᮬ࡙۫۫🖤🖤🖤꒱ ׁ 𝂅ׄ𓆠゙ִ ۣʾ࿙ֺ࿙ᮬֺ ⸼ ֿؗ ִֺ 𝆋ܹ᷼🤩˛ִִ ֺ ۣ𝂅ׄ𝂅ׄ𝅄
custom 542235163802943749620custom 537305912730193828616custom 537331956123386847012custom 52985865547578482419custom 52514311982819723598custom 53733246164103754327
Sticker, posted without a caption
🎀🎀🎀ִ ៸ 🪄˛ִִ ֺ ۣ𝅄 ִ۫ ུུ𝅄 ॒𝕃𝑜ֺ𝐯ℯ ִ l𝗂ᩚ𝒔໋݄ȶ˛ִִ⸼𝂅ׄ 𝅄 ִ ៸ִ៸𝅄 ִ۫🤩 ៸ִ៸ ݃𓈒🤩𝗂ᩚ𑜀ֺթִּׄ𝑎ᮬ͜𔘓ִ𝆬🤩🎀🎀🎀🎀🎀🎀🎀🎀🎀 Порядок не имеет значения 670, 𝗂ᩚꬻ𝐯𝑎ᮬ͜𝕝𝗂ᩚd, 𝐫𝐮b𝗂ᩚꬻ, 𝑎ᮬ͜𝕝թִּׄh𝑎ᮬ͜, b𝐮𝗂ᩚ𝕝dℯ𝐫, ẜ𝐫𝑜ֺ𝐳꯭ℯꬻ, 𝖪𝑜ֺ𝐠𝒔໋݄𝑡𝗂ᩚ
custom 542235163802943749628custom 537305912730193828620custom 536391360862542393919custom 52985865547578482419custom 53733246164103754329custom 52514311982819723598custom 53733195612338684708
Sticker, posted without a caption
𝆕 𝅘𝅥𝅮 ִִֵ᳕۫𝅄︵ֺ ॒𝅄🤍𝑒ֺ𝐯𝑒ֺꬻ🤩h𝑒ֺ ִ𝕙𝗂ᩚ𑜀ֺ/.𝑎ᮬ͜ꬻყ᪶⊰࡙ ִ𝇌ׄ ݃𓈒📼📼 𐨂 ྀི ໋݄ ⸼ ˛ִִ ֺ ۣ 🎀 𑇓𝆬⃝🎇05. 03🤩15 ყ᪶.𝑜ֺ🤩𝔦ׅꬻ𝑡թִּׄ 𝆕 ִֵ᳕۫ 𝅄⎯꯭𝆕 ִֵ᳕۫ ︵᷼ ִֺ۪ 𝅄 🎀🎶𝅄pl𝑎ᮬ͜ყ᪶𝕝𝔦ׅsȶ ₊💿 ༢ུ🪄sẜթִּׄ l𝔦ׅ𝕟k𑇓𝆬 ༢ུ🪄𝒶ֺ︩︪֪𝒏݊𐐫ֺ͜𝒏݊🪄
custom 542235163802943749625custom 536391360862542393917custom 537305912730193828617custom 525143119828197235911custom 529858655475784824111custom 537332461641037543211custom 537331956123386847010
Sticker, posted without a caption
File, posted without a caption
custom 542235163802943749615custom 537305912730193828610custom 52514311982819723599custom 52985865547578482419custom 53639136086254239398custom 53733195612338684708custom 53733246164103754327
Channel created
Showing the 9 most recent of 9 posts we hold for @infosoftcore. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
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.
@infosoftcore named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 18 October 2026 — this entry's latest reading, not the date you are reading this.
“[𝗜𝗡𝗙𝗢] ᨦSᨵfִɬׁCᨵꭉִꫀִׄദ” (@infosoftcore), 1 subscribers as measured 18 October 2026. Telegram Register, tgregister.com/channel/infosoftcore.
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.