Sticker, posted without a caption

Channel
𝐕 ⿻
@vaelinks
On this record: Growth · Engagement · Posts · Citations · Cite this entry
126subscribers
+0 since we began measuring on 29 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001725079567 |
|---|---|
| Type | Channel |
| Username | @vaelinks |
| Description | 自己的群链接&有管理的群链接 — 𝐌𝐀𝐘 𝟑 𝟎 . |
| Created | 30 May 2022 — measured — dated from the channel’s first post |
| First recorded | 29 September 2026 |
| Last confirmed live | 29 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/vaelinks |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Sept 2026, 07:22 | 126 | no change |
| 29 Sept 2026, 06:48 | 126 | first reading |
Engagement
8 posts held, back to 30 May 2022 — 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 8 posts for this entry, the most recent from 14 March 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
目前只接的业务⬆️ 🤩 算卦/八字运势/接下来一年的运势 🥰 提供中间人服务 了解代交详情 @jiaoyizjgy 📣 租号没做了 摆着信誉群罢了🐺
🥰
其他群 💠 微信扫码群 🥰 ꒰ @wxsaomaqunv ꒱ 算卦·租号信誉⚡ ꒰ @sgxinyuqun @jiezhangvl ꒱ 非诚勿扰 💌 ꒰ @feichengwurao1 ꒱ 微信互加群 💊 ꒰ @weixinhujiaqu ꒱ 动漫卡点群 😰 ꒰ @animateamv ꒱ 聊天群 🍉 ꒰ @liaotianqunva ꒱ 福利群 💰 ꒰ @ganyu_fuliqun ꒱ 美化白嫖群 🧦 ꒰ @baipiaogy ꒱ 美化广群 🐶 ꒰ @meihuagy ꒱ 有管理 音乐群 🎧 ꒰ @hayashiplaylist ꒱ 腐腐群 😉 ꒰ @fufuboiluv ꒱
买卖 | 宣传群 💠 ꒰ @vmmqun ꒱ ꒰ @qxcqun ꒱ ꒰ @kazummq ꒱
投稿社 ⭐ 𝗚𝗬 投稿群 ❤️ (看置顶) ꒰ @tougaoshegy ꒱ 揭发群 ⛔ ꒰ @jiefaqunv ꒱ UP/DOWN群 ✅ ꒰ @updowngy ꒱ 吵架发泄社 👊 ꒰ @chaojiaqunv ꒱ 有管理员 💳 @swtougao @shikimoritg1025
ꗃ @VAEUIZX '𝗦 𝗟𝗜𝗡𝗞𝗦 ⭐
Channel created
Showing the 8 most recent of 8 posts we hold for @vaelinks. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@animateamv · 5211 post૮ ᴠʏᴜ ა
@baipiaogy · 3811 post来吵架吗’?
@chaojiaqunv · 2,0371 post非诚勿扰 𓄹
@feichengwurao1 · 1,4061 postふじょし‧₊
@fufuboiluv · 1651 post𝐺𝑎𝑛𝑌𝑢 𓆡🧧
@ganyu_fuliqun · 3,0501 postGY 代交服务
@jiaoyizjgy · 5581 post揭 发 群 ˖﹅
@jiefaqunv · 6,4941 post【 𝐕 宣传群 】🉑刷屏
@qxcqun · 1,4061 post𝚂𝙷𝙸𝙺𝙸𝙼𝙾𝚁𝙸 投稿群 ‘࣪˖ ๋
@shikimoritg1025 · 2231 post灵界投稿社
@swtougao · 2381 post你们好 直接看置顶
@tougaoshegy · 2,2011 post𝖀𝖕 / 𝕯𝖔𝖜𝖓
@updowngy · 7,1281 post𝐕 𝐌 𝐌 交易群 ˎˊ ֢
@vmmqun · 1,4411 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.
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 29 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐕 ⿻” (@vaelinks), 126 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/vaelinks.
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.