Tolong jangan ketuker ya lojis, nanti tenggelam dan ga sempat ke fw kalau kalian send ke bot sfs.

Channel
YULLOGIC : CASEBOOK ARCHIVE. 📜
@Yullogic
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
1,704subscribers
-526 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1004441592315 |
|---|---|
| Type | Channel |
| Username | @Yullogic |
| Created | Between 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/Yullogic |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 04:17 | 1,704 | -128 |
| 3 Sept 2026, 15:00 | 1,832 | -32 |
| 31 Aug 2026, 11:24 | 1,864 | -28 |
| 28 Aug 2026, 20:37 | 1,892 | -55 |
| 25 Aug 2026, 14:11 | 1,947 | -56 |
| 22 Aug 2026, 13:23 | 2,003 | -124 |
| 19 Aug 2026, 11:16 | 2,127 | -134 |
| 16 Aug 2026, 20:24 | 2,261 | +29 |
| 13 Aug 2026, 05:16 | 2,232 | -19 |
| 9 Aug 2026, 18:24 | 2,251 | +18 |
| 6 Aug 2026, 21:50 | 2,233 | +3 |
| 6 Aug 2026, 09:38 | 2,230 | first reading |
Engagement
39 posts held, back to 5 August 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 2 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 39 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
14 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 28.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 4 | 28.6% | |
| ❤🔥 | 3 | 21.4% | |
| 🎉 | 3 | 21.4% | |
| 🆒 | 2 | 14.3% | |
| ❤ | 1 | 7.14% | |
| 🥰 | 1 | 7.14% |
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 4 of the 39 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 14 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 5 August 2026 to 7 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
Sticker, posted without a caption
Selamat pagi lojis, mengingatkan kembali untuk kebutuhan HFW tolong ke bot @Yullogicbot, sedangkan untuk kebutuhan SFS dan Replace ke bot @Yullogicsfsbot. Semoga tidak ada yang nyasar lagi ya😍🖐
Sticker, posted without a caption
Sticker, posted without a caption
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ (+88 CUE) Call. 📞 🎱 SHOTS / هدف ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ
Haii
ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ ©️ HOSEALS ㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ ㅤㅤㅤㅤㅤ
❤🔥1🥰1
Sticker, posted without a caption
Sticker, posted without a caption
ㅤㅤ ㅤ(HFW) GLITCHY SUBS — FOR — SUBS ⚠️ ..? ㅤㅤㅤN3ØN GL!TCH ¥3–7 PROTOCOL ㅤㅤ#STATIC signals flicker through the grid, ㅤㅤneon circuits pulse beneath synthetic ㅤㅤskins, (+777) data becoming their ㅤㅤnew identity. @AHNGLITCHSFS_BOT ㅤㅤ
Sticker, posted without a caption
Showing the 12 most recent of 39 posts we hold for @Yullogic. 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.
Polls
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
This or That
- Deket sama orang bingung57%
- Deket sama orang tukang ghosting43%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
This or That
- Langsung tukeran40%
- Nunggu udah lumayan nyaman60%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
This or That
- Backstreet0%
Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.
This or That
- Tetep pacaran walau temen circle ga setuju50%
- Tetep hts aja50%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 39 most recent posts we hold, published 5 August 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@EOMIAHNCER · 2,2172 postsCHADZUMI: HOLD SFS.
@CHADZUMI · 1,9761 post[FREE UNSUBS] Fallen Within Bin; Arrows 𝓸𝓯 Affection. ♥️༄˳
@FallenWithinBin · 2,0621 postFawibi Archive.
@fwbarchive · 151 postghosts, @blissyian .. ♡
@gjhosts · 21 postGLAMPAGES.
@GLAMPAGES · 61 post𝙹𝚄𝙿𝙰𝚆𝚂 🐈 @VAORUE
@Jupaws · 1,9411 postarsip @seokverse
@seokkverse · 81 post✷ SEOKVERSE #3rdLockWithRiize
@Seokverse · 1,4681 post
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 13 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.
@chromejeans · 2,5134 postsRaceYulz.
@RaceYulzz · 182 postsBBOYNEXTZ ARCHIVE 📂
@BBOYNEXTZHIVE · 931 postRepository DEMOONEST
@DEMOONESTs · 191 postGeonix Archive.
@Geonixzzip · 161 postGAMEGYUL SAVE-POINT
@GYULOGS · 211 post[HOLD SFS] JIWOOREVE: Sorrow Of Blind Heartfelt. OPGATE!
@jiwooreve · 3,0651 postarchive-𝘴𝘩𝘢𝘥𝘰𝘸𝘴
@mytheomians · 201 postObscort's Record.
@ScortChive · 211 postSuwi’s .. 🏖️
@Stelwards · 111 post˖`💧❀ ✴️ ݁. 𝚠𝚑𝚒𝚜𝚙𝚎𝚛𝚢𝚞𝚕 ░ °₊ ୭
@whisperyul · 1,3381 postMARK OF ©WVS
@WOOVSN · 81 postYinsvelour arsip
@Yinsvelourr · 101 post
Names
Channels on the register whose handles appear in this channel's posts.
@username · 1,315,7212 postsCHADZUMI: HOLD SFS.
@CHADZUMI · 1,9761 post♡ 𝙲. 𝙻𝙾𝙴𝚅 ~ 𝒾an : *.゚𓎟ྀི
@cloevian · 5,0091 postCØRPHALT — MOTORS VICIOUS
@CorPhalt · 2,9841 postGYULORY.
@GYULORY · 2,1451 postHYUCKRUST: Built to Run
@hyuckrust · 1,6551 posthyunella 𖣠
@hyunellas · 111 postJOKERSEAN. [🃏]
@JokerSean · 2,6531 post𝙹𝚄𝙿𝙰𝚆𝚂 🐈 @VAORUE
@Jupaws · 1,9411 post(rpin!) 𝚕𝚎𝚎𝚊𝚗𝚘𝚛𝚎 ⁕
@leeanore · 2,2941 postLEEANOTHER.
@Leeanother · 3,5801 postDISBAND. 𝘭𝘰𝘵𝘶𝘴𝘳𝘮𝘦𝘯. ‧₊˚ 🌸 ๑ “beneath lotus skies.” ♡
@lotusrmen · 1,2111 post(REST) naderria: shop in love.
@Naderria · 3,4801 post[HOLD SFS] 𝘖𝘝𝘝𝘚𝘐𝘙𝘌 : MEOVV DESIRE.
@OVVSIRE · 1,3301 postPETITAESAN
@petitaesan · 1,4021 postSEANLEAGUE: PRAECLARUS IMPERIUM.
@SeanLeague · 5,0121 post𖦹 Vicky Soirée: #22PrintsOfVickySoiree.
@vickysoiree · 1,9781 postviveeans, you’ll be missed ♡
@viveeans · 7751 postDISBAND
@VORSCAR · 1,1221 postWIREHYUL.
@Wirehyul · 2,1581 postWonchestra: The Hall Of Midnight Serenade
@wonchestra · 2,6301 postThe Depth Of WONMARINE.
@wonmarine · 1,9511 postXINTORY: Built from stardust.
@Xintory · 1,7841 post◌* 𓂃˖˳· yuhα:gloss 🫖♥
@yuhagloss · 3,2961 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Yullogic named 2 handles 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.
Evidenced gone
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.
named in 2 posts, 8 August 2026 – 8 August 2026 · confirmed gone 25 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 8 August 2026 – 11 August 2026
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“YULLOGIC : CASEBOOK ARCHIVE. 📜” (@Yullogic), 1,704 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Yullogic.
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.