Channel
@solo_q_q
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
56,567subscribers
-318 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001933683239 |
|---|---|
| Type | Channel |
| Username | @solo_q_q |
| Description | Бабки не проблема: @solo322 Сотрудничество: @onleeking |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/solo_q_q |
Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 44% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 21:19 | 56,567 | +124 |
| 16 Sept 2026, 11:01 | 56,443 | +41 |
| 14 Sept 2026, 16:37 | 56,402 | -62 |
| 13 Sept 2026, 03:37 | 56,464 | +69 |
| 11 Sept 2026, 06:58 | 56,395 | +2,038 |
| 8 Sept 2026, 13:18 | 54,357 | -83 |
| 5 Sept 2026, 08:17 | 54,440 | -145 |
| 3 Sept 2026, 08:56 | 54,585 | -93 |
| 2 Sept 2026, 04:52 | 54,678 | -1,837 |
| 1 Sept 2026, 04:04 | 56,515 | +115 |
| 31 Aug 2026, 01:38 | 56,400 | -65 |
| 30 Aug 2026, 00:37 | 56,465 | -48 |
| 29 Aug 2026, 00:05 | 56,513 | -375 |
| 28 Aug 2026, 02:16 | 56,888 | -70 |
| 27 Aug 2026, 04:18 | 56,958 | -85 |
| 26 Aug 2026, 00:46 | 57,043 | -144 |
| 25 Aug 2026, 00:15 | 57,187 | +153 |
| 23 Aug 2026, 14:17 | 57,034 | +1,776 |
| 22 Aug 2026, 03:47 | 55,258 | +254 |
| 20 Aug 2026, 19:35 | 55,004 | first reading |
120 posts held, back to 12 July 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 106 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 120 (12 July 2026 – 22 September 2026) |
| Views total | 1,344,200 |
| Reactions total | 16,888 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Sept 2026, 07:23 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 23 September 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.
Measured directly from 6 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.
27,938 reactions across 117 posts, in 16 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5258403626715479005 | 10,669 | 38.2% | |
| custom 5384292347976640592 | 6,007 | 21.5% | |
| custom 5395574857696050944 | 3,950 | 14.1% | |
| custom 5384080090692873493 | 2,805 | 10.0% | |
| custom 5192884424601013486 | 1,225 | 4.38% | |
| custom 5193155780634776245 | 1,068 | 3.82% | |
| custom 5384490620846892713 | 557 | 1.99% | |
| custom 5195459923214895057 | 411 | 1.47% | |
| custom 5384275284071575784 | 354 | 1.27% | |
| custom 5316713391216159315 | 277 | 0.991% | |
| custom 5469891312473909535 | 209 | 0.748% | |
| custom 5467456452564134216 | 191 | 0.684% | |
| custom 5298732931538267842 | 172 | 0.616% | |
| custom 5469721601136171252 | 25 | 0.089% | |
| custom 5381976381351552514 | 12 | 0.043% | |
| custom 5384108544851207801 | 6 | 0.021% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 117 of the 120 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 27,938 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 120 most recent posts we hold, published 12 July 2026 to 22 September 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| KW2aPRYdr5QoPXHUHdcgTCt4YvVMXRbzXgm5jt2GVqmW9XeS5o1yNCX7TEKTsATf | 1 | 13 August 2026 | 13 August 2026 |
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 120 most recent posts we hold, published 12 July 2026 to 22 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Melharucos > gpk + kiyotaka Чел ноль раз умер против 15к ммр человек. Это 1к ммр по вашему? Найс челы своего друга задрота продвинул на турик… Я уже пишу жалобу организатором, ждите 😤
custom 5258403626715479005329custom 5192884424601013486105custom 531671339121615931542
Posted without readable text
custom 531671339121615931553custom 538408009069287349332custom 525840362671547900515
Первая игра стримерс батла уже на ютубе 🕺 📺 Team Solo vs Team Daxak
custom 525840362671547900539custom 529873293153826784219custom 53955748576960509447
Причина поражения — украли пугну у Андера Завтра в 15:00 против Данька и Глебасика, приходите поддержать Алабая ❤️
custom 5258403626715479005132custom 538408009069287349339custom 519315578063477624510
🎉 Розыгрыш завершен! 🏆 Победители: 1. @teramisusl1k 2. @lex4ndr 3. @costa_prosto 4. @SaintQ25 5. @Oeedap123ao1 6. @vova_neok 7. @AleksandrLoginov99grs 8. @sas098523mh 9. @haaftiko1f 10. @copen_hagen_paris Победителям в ближайшее время отпишет @VaxpEe 🔍 Проверить результаты
custom 538408009069287349316custom 53167133912161593156
Posted without readable text
custom 5298732931538267842153custom 538429234797664059214custom 53840800906928734938
Разъебали нубов за 6 минут. Тренировки окончены. Сильному не нужны, слабому не помогут
custom 5395574857696050944134custom 538429234797664059227custom 525840362671547900513
Так поступают только лучшие друзья 😁
custom 5258403626715479005164custom 538429234797664059266custom 51928844246010134869
Клановые войны в 17:30 ❤️
custom 5258403626715479005166custom 519288442460101348640custom 519545992321489505718
Киберспортивному выпуску соотвествующий розыгрыш 😎 Запускаем конкурс с Лёхой! Призы для кайфовых каток: 1. Мой игровой ПК и LCD монитор 2. Наушники Lunacy Louder 3. Мышка Lunacy Another One Подписывайтесь на Smo10v и Solo, жмите кнопку «ЛУТ» и ждите итоги 2 октября 🔥
custom 525840362671547900551custom 538429234797664059222custom 539557485769605094413
Posted without readable text
custom 5258403626715479005153custom 519288442460101348638custom 538408009069287349312
Сегодня без потокового вещания. Пора командой тренироваться к БСБ. КВшки завтра делаем или не стоит, че думаете?
custom 5395574857696050944132custom 519545992321489505719custom 519315578063477624513
Showing the 12 most recent of 120 posts we hold for @solo_q_q. 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.
@solo_q_q edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Победитель EWC 2026
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 120 most recent posts we hold, published 12 July 2026 to 22 September 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.
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.
Named by 10 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Solo” (@solo_q_q), 56,567 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/solo_q_q.
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.