Telegram RegisterThe public register of Telegram
Telegram profile photo for SPStudio & Market

Channel

SPStudio & Market

@spStudioMarket

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

262subscribers

-9 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001450426652
TypeChannel
Username@spStudioMarket
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/spStudioMarket

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.

Growth

262271266.57 August 2026 — 271 subscribers7 August 2026 — 271 subscribers21 August 2026 — 269 subscribers29 August 2026 — 266 subscribers16 September 2026 — 262 subscribers7 August 202616 September 2026
5 measurements spanning 40 days, net -9. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 261–272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 13:00262-4
29 Aug 2026, 09:36266-3
21 Aug 2026, 10:13269-2
7 Aug 2026, 04:31271no change
7 Aug 2026, 04:22271first reading

Engagement

20 posts held, back to 24 February 2022the 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 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

52 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2650.0%
👍1630.8%
👎47.69%
🔥47.69%
👏11.92%
🤩11.92%

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 14 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 52 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 24 February 2022 to 20 July 2025, 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

20 Jul 2025, 00:29 UTC169 views5 reactionsread 7 August 2026

Is there any activity? We will resume project production.

3👍1🔥1

3 May 2023, 21:29 UTC861 views4 reactionsread 7 August 2026
Photo

Hello everyone, I would like to present you my new icon pack. In order to use the icon pack, you need to download "Icon Pack Studio" from google play. I posted the link below. You can access more of my icon packs by clicking the profile. 🆙 https://play.google.com/store/apps/details?id=ginlemon.iconpackstudio 💡 You can donate to us as much as you want from the pinned message so that we can get paid for our efforts.

2👍1🔥1

14 Apr 2023, 22:49 UTC817 views1 reactionsread 7 August 2026
Photo

📣 Announcement: I wanted to expand the content of my channel. I am changing the concept completely upon customizing your Mobile Devices. These are Wallpaper, Self Made Widgets, My Telegram Themes (Likewise our telegram themes will continue as projects.), our Icon Packs (via app), and I'm here to provide more. All of the projects will be specially prepared and published. Our first post starts on April 17th. The futur

👍1

14 Apr 2023, 12:04 UTC654 views4 reactionsread 7 August 2026

NEWS! Our channel is becoming a studio from start to finish and we're getting a big update. We are returning this week in a very different way. Stay tuned. ✨

3🔥1

13 Jun 2022, 20:15 UTC≈8,310 views5 reactionsread 7 August 2026
Photo

⁣⁣👁️ lovely. #️⃣ Tags: #mobile #white #spthemes ✨ Channel: @spThemes

👍4👎1

3 May 2022, 21:52 UTC≈18,800 views5 reactionsread 7 August 2026
Photo

⁣⁣👁️ tired eyes. #️⃣ Tags: #mobile #dark #blue #spthemes ✨ Channel: @spThemes

👍3👎2

27 Apr 2022, 20:33 UTC≈10,700 views1 reactionsread 7 August 2026
Photo

⁣⁣❇️ Blue Katanas. #️⃣ Tags: #mobile #dark #blue #spthemes ✨ Channel: @spThemes

1

27 Apr 2022, 20:22 UTC≈5,490 views3 reactionsread 7 August 2026
Photo

⁣⁣❇️ blurry future. #️⃣ Tags: #mobile #dark #purple #spthemes ✨ Channel: @spThemes

2👍1

30 Mar 2022, 20:14 UTC≈6,720 views1 reactionsread 7 August 2026

⁣⁣❇️ Nice Night. #️⃣ Tags: #mobile #dark #purple #spthemes ✨ Channel: @spThemes

👎1

22 Mar 2022, 20:26 UTC≈9,260 viewsread 7 August 2026

⁣⁣❇️ great love. 🌆 #️⃣ Tags: #mobile #dark #purple #spthemes ✨ Channel: @spThemes

Showing the 12 most recent of 20 posts we hold for @spStudioMarket. 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

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“SPStudio & Market” (@spStudioMarket), 262 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/spStudioMarket.

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.