16 Jan 2024, 17:09 UTC890 viewsread 14 August 2026
Photo
💿 ›› фото ≠ пнг ˋˏ материал в коммах ▸ ‹‹ #png ›› ⇌ @wifcodes
Channel
ˊˎ 𝘸𝘪𝘧𝘤𝘰𝘥𝘦𝘴 ˒
@wifcodes
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
26subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002079589213 |
|---|---|
| Type | Channel |
| Username | @wifcodes |
| Created | 7 January 2024 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/wifcodes |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 12:08 | 26 | no change |
| 14 Aug 2026, 09:03 | 26 | first reading |
Engagement
13 posts held, back to 7 January 2024 — 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 pageof 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 13 posts for this entry, the most recent from 16 January 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 6s
- Average length
- 6s
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.
Recent posts
12 Jan 2024, 18:25 UTC840 viewsread 14 August 2026
Photo
🍒 ›› xml ≠ шрифты ˋˏ материал в коммах ▸ ‹‹ #font ›› ⇌ @wifcodes
11 Jan 2024, 16:26 UTC771 viewsread 14 August 2026
Photo
🍞 ›› сс ≠ колоринг ˋˏ материал в коммах ▸ ‹‹ #coloring ›› ⇌ @wifcodes
10 Jan 2024, 14:48 UTC≈1,060 viewsread 14 August 2026
Video
💄 ›› пак ≠ шейки ˋˏ материал в коммах ▸ ‹‹ #shake ›› ⇌ @wifcodes
9 Jan 2024, 18:35 UTC≈1,220 viewsread 14 August 2026
Photo
💐 ›› xml ≠ шрифты ˋˏ материал в коммах ▸ ‹‹ #font ›› ⇌ @wifcodes
8 Jan 2024, 14:10 UTC≈1,030 viewsread 14 August 2026
Photo
✨›› пак ≠ на 200 пдп ˋˏ материал в коммах ▸ ‹‹ #coloring ›› ⇌ @wifcodes #translation #font #shake
8 Jan 2024, 14:01 UTC567 viewsread 14 August 2026
спасибо большое за 200, мы вас любим❤️❤️ скоро выложим пак
7 Jan 2024, 20:40 UTC640 viewsread 14 August 2026
ойй уже 100, спасибо вам❤️❤️
7 Jan 2024, 19:57 UTC≈1,610 viewsread 14 August 2026
Photo
🌹 ›› код ≠ колоринг ˋˏ ссылка ▸ ‹‹ #coloring ›› ⇌ @wifcodes
7 Jan 2024, 16:45 UTC≈1,800 viewsread 14 August 2026
Photo
✨ ›› код ≠ колоринг ˋˏ ссылка ▸ ‹‹ #coloring ›› ⇌ @wifcodes
7 Jan 2024, 16:11 UTC534 viewsread 14 August 2026
https://t.me/wifcodes?boost голосуйте
7 Jan 2024, 16:05 UTC556 viewsread 14 August 2026
🌹 инфо @wifcodes 🦋вп - 0+ с подпиской на канал (вкл звук) и с реакцией на пост в закрепе 100+ только с реакцией на пост в закрепе 💋сразу скрины и шб 💋отписка - бан, ап, жалобы 💋шб держим 15-20 мин 🦋оп - 5-100, со скрином добиваем через @giftanyas 🦋приход - 1-10, со скрином 💋не добили? бан, ап, жалобы 💋ТОЛЬКО ПОПРОБУЙТЕ ЭТИХ АРАБОВ ПРИВЕСТИ 💋по всему писать @kidsssq // @melqw
Showing the 12 most recent of 13 posts we hold for @wifcodes. 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.
Citation-graph rank
Citation-graph rank — 297,158 of 1,480,688entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“ˊˎ 𝘸𝘪𝘧𝘤𝘰𝘥𝘦𝘴 ˒” (@wifcodes), 26 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/wifcodes.
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.