Channel photo updated

Channel
𝑼𝑷 𝑨𝑳𝑳 𝑵𝑰𝑮𝑯𝑻.
@marketskie
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001608232762 |
|---|---|
| Type | Channel |
| Username | @marketskie |
| Description | 𝗼𝘄𝗻𝗲𝗿𝘀 :: @dalssas 𝙖𝙙𝙢𝙞𝙣𝙞𝙨𝙩𝙧𝙖𝙩𝙞𝙤𝙣: @ahaha_fuk @Umymae @qwe_990 союзы: @dalssas |
| Created | Between 1 December 2021 and 12 November 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/marketskie |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 05:15 | 7 | no change |
| 31 Aug 2026, 05:00 | 7 | first reading |
Engagement
20 posts held, back to 12 November 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 20 posts for this entry, the most recent from 20 January 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 9
- Videos
- 14
- Links
- 2
Lifetime counters from Telegram’s own channel header, read 31 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 31s
- Average length
- 6s
Measured directly from 5 videos 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.
Reaction mix
12 reactions across 6 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤🔥 | 3 | 25.0% | |
| 👍 | 3 | 25.0% | |
| 🔥 | 3 | 25.0% | |
| 🍓 | 1 | 8.33% | |
| 💔 | 1 | 8.33% | |
| 🥰 | 1 | 8.33% |
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 6 of the 20 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 November 2022 to 20 January 2023, 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
. . ± (💨)) unio.n !¡ ву вау вау йупи йо йупи йей ( @mondeers )) я иду в клуб (@marketskie )) они такие - ээээй!)01)0)) прекрасного союза!¡
Signed ((🪷) treat me like a slut little dirty bitch, yeah, I love to fu
𝑼𝑷 𝑨𝑳𝑳 𝑵𝑰𝑮𝑯𝑻. pinned «🚨для союзников🚨 значит так. я немного проебался в плане союзов. прошу оставить юз канала в комментариях, с которым у нас союз. серьёзно нужно уже. #ᴍᴀʀᴋᴇᴛsᴋɪᴇ_rp (не рп. это чтобы заметили.)»
АХ ТЫ СУКА.
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
🚨для союзников🚨 значит так. я немного проебался в плане союзов. прошу оставить юз канала в комментариях, с которым у нас союз. серьёзно нужно уже. #ᴍᴀʀᴋᴇᴛsᴋɪᴇ_rp (не рп. это чтобы заметили.)
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
это мне пишут а я на тебя перенаправляю кстати ХАХАХАХ
Signed ляпота
союзники нас всё трахают и трахают.
❤🔥1💔1
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
@vix_vx ᴛᴩᴀхнуᴧи ʙ ᴨᴏᴨᴋу @marketskie Ꮋᴀдᴇᴇʍᴄя нᴀ дᴏᴧᴦий и ᴋᴩᴇᴨᴋий ᴄᴏюɜ, ᴋᴩᴇᴨᴋий ᴋᴀᴋ нᴏᴋиᴀ! Ꮯᴧᴇдящий ɜᴀ ʙᴀʍи: @jok_kook
❤🔥1
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
нᴀ ᴨᴏʙᴏдᴏᴋ @thisbloodynight ᴨᴏᴨᴀᴧся @marketskie бᴏᴧьɯᴇ ʙᴀᴄ нᴇ ᴏᴛᴨуᴄᴛиʍ)
❤🔥1👍1
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
━━━━━━━━━━━━━━━━━━━━━━━━━━━ В этот прекрасный вечер @The_LastStar пригласили чудесных @marketskie вместе посмотреть на звёздное небо. Надеемся на крепкий союз ! ━━━━━━━━━━━━━━━━━━━━━━━━━━
Signed `🎄𝗓𝗑𝖼 𝗁𝗎𝗇𝗍'𝖾𝗋. #bi8l ` ˢᵇʰ
ᥴуʍᥱρκᥙ ᥴᴦущᥲ᧘ᥙᥴь ᥙ ᧐κуᴛыʙᥲ᧘ᥙ ʙᥱᥴь ᴦ᧐ρ᧐д ᴛёʍн᧐ᥔ ᥰᥱ᧘ᥱн᧐ᥔ. ʙ ϶ᴛу ᥰ᧐-нᥲᥴᴛ᧐ящᥱʍу ᥴᴛρᥲɯную н᧐чь @marketskie ɜᥲδρᥲ᧘ᥙ ᥴᥱρдцᥱ ᥙ дуɯу чудᥱᥴных @xdsamurais ᥰρᥙᥴʙ᧐ᥙʙ ᥴᥱδᥱ. нᥲдᥱᥱʍᥴя нᥲ д᧐᧘ᴦ᧐ᥱ ᥴ᧐ᴛρуднᥙчᥱᥴᴛʙ᧐ ᥙ ʙᥱρн᧐ᥱ ᥴ᧘ужᥱнᥙᥱ дρуᴦ дρуᴦу.
Signed ❲❄️❳⋅ ..⃗. 𝐙𝐗𝐇𝐀𝐍𝐓𝐄𝐑. #bi8l
хантер пидорас уебан еблан кароче пиздатый чел вот блог хантера кстати: @hanssass можете меня ещё по ебальнику пиздить за не акт. жестоко насрал без запятых.
👍2🍓1
Signed ❲🍂❳⋅ ..⃗. 𝐙𝐗𝐇𝐀𝐍𝐓𝐄𝐑. #bi8l
Showing the 12 most recent of 20 posts we hold for @marketskie. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 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.
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“𝑼𝑷 𝑨𝑳𝑳 𝑵𝑰𝑮𝑯𝑻.” (@marketskie), 7 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/marketskie.
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.