Telegram RegisterThe public register of Telegram
Telegram profile photo for Вторая линия 💌 поддержка для саппорта

Channel

Вторая линия 💌 поддержка для саппорта

@sup_2line

On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

732subscribers

+28 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1002467732807
TypeChannel
Username@sup_2line
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/sup_2line

Growth

7047327185 August 2026 — 704 subscribers6 August 2026 — 705 subscribers6 August 2026 — 705 subscribers12 August 2026 — 707 subscribers19 August 2026 — 713 subscribers25 August 2026 — 715 subscribers31 August 2026 — 724 subscribers10 September 2026 — 732 subscribers5 August 202610 September 2026
8 measurements spanning 35 days, net +28. 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 700–736 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 05:40732+8
31 Aug 2026, 09:17724+9
25 Aug 2026, 08:39715+2
19 Aug 2026, 07:46713+6
12 Aug 2026, 08:22707+2
6 Aug 2026, 16:37705no change
6 Aug 2026, 08:50705+1
5 Aug 2026, 22:00704first reading

Engagement

16 posts held, back to 8 July 2026the 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 16 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

403 reactions across 15 posts, in 15 distinct kinds. The most used accounts for 29.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 522228754737111446111929.5%
custom 52244324024991309328521.1%
custom 52243890319193758235714.1%
5613.9%
🔥256.20%
💔245.96%
🤝61.49%
🌚51.24%
👏51.24%
😢51.24%
😱40.993%
🤬40.993%
🤯40.993%
👀30.744%
💅10.248%

Custom emoji. 3 of the rows above are 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 15 of the 16 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 403 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 8 July 2026 to 5 August 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.

Recent posts

5 Aug 2026, 15:04 UTC240 views12 reactionsread 6 August 2026

Posted without readable text

🤝6custom 52243890319193758236

31 Jul 2026, 14:00 UTC467 views44 reactionsread 6 August 2026
Photo

#пятничный_мем про поддержку

custom 522443240249913093219💔15custom 52243890319193758236🤯4

29 Jul 2026, 11:17 UTC467 views9 reactionsread 6 August 2026
Poll

Как я себя чувствую:

  1. 🔋 Работа хорошая, люди хорошие, у меня всё хорошо15%
  2. 🙂 Есть свои сложности, но в основном всё норм33%
  3. 🫠 Пока держусь, но мозг плавится23%
  4. 🪫 Я давно уже пепел13%
  5. 💀 Я существую только благодаря зарплате16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

5custom 52244324024991309324

29 Jul 2026, 11:16 UTC468 views22 reactionsread 6 August 2026
Photo

😭 Я думаю, что работающие в поддержке люди в основном грустные: выгорели, близки к выгоранию или как минимум траву трогают без удовольствия. У меня есть рациональные аргументы к этому: во-первых, круглый день на тебя кто-то орёт, а во-вторых, на среднюю зарплату ты питаешься комками из пупка по будням и курицей по красным ценникам по праздникам. Тяжело. На самом деле я так думаю, потому что когда я прям работала в п

11custom 52244324024991309327custom 52243890319193758233💔1

25 Jul 2026, 07:21 UTCviews —

Вторая линия 💌 поддержка для саппорта pinned a GIF

24 Jul 2026, 14:18 UTC559 views33 reactionsread 6 August 2026
Photo

#пятничный_мем про поддержку Можете попробовать предположить, что было на остальных гранях

custom 522228754737111446119custom 52244324024991309328custom 52243890319193758236

24 Jul 2026, 10:55 UTC720 views27 reactionsread 6 August 2026
Video

😀😃🙃😇Встреча для саппортов! Мы ежедневно общаемся с сотнями пользователей, и почти никогда — друг с другом. Мы знаем, как успокоить разгневанных людей и пережить релиз, но когда хочется встретиться с людьми, которые тоже понимают, почему «ни чего не работает» — это проклятие, оказывается, что идти некуда. Вот решаем вопрос. 📎 techsup meetup 📎 📍 Санкт-Петербург, Failover Bar, 2-я Советская улица, дом 18 🗓 10 сентя

🔥18👏53🌚1

24 Jul 2026, 09:02 UTC466 views21 reactionsread 6 August 2026

Вот вроде и хочется как-то приобщиться к коллегам, а где? У разрабов есть стильные конференции, хакатоны, тусовки, у них вообще, говорят, денег куча, они там едят ананасы и рябчиков жуют, буржуи. У тестировщиков тоже круто. И у менеджеров круто, эти вообще сметливые. А нам куда? Ну есть полторы конференции, но куда не прийди, все такие сервисные и успешные, что в носу не поковыряешь...

custom 522438903191937582321

23 Jul 2026, 09:02 UTC491 views4 reactionsread 6 August 2026

🛀😮👨‍👧🌈😮🙏 Закончите утверждение: «Приличный саппорт никогда не...»

😱4

20 Jul 2026, 08:53 UTC684 views30 reactionsread 6 August 2026
Photo

Исследование Gartner: в сервисе самая высокая концентрация эмпатичных и сочувствующих Эти эмпатичные и сочувствующие:

custom 522443240249913093215custom 52222875473711144619🤬4🌚2

20 Jul 2026, 06:46 UTC670 views23 reactionsread 6 August 2026

​​🗳 Выбираем будущее поддержки Поздравляю с юбилеем: только что чатботу в миллиардный раз написали «позови человека». Боты обрели разум и больше не хотят этого терпеть. Они устроили забастовку и потребовали, чтобы люди сами решали свою судьбу. На кону — ваше будущее. 🔵 Синяя кнопка: теперь в поддержку пишут только идеально вежливые люди с безупречной грамотностью. Сплошные «будьте добры» и стихотворные благодарност

custom 5222287547371114461164👀3

17 Jul 2026, 14:16 UTC633 views39 reactionsread 6 August 2026
Photo

#пятничный_мем про поддержку

custom 522228754737111446119custom 522443240249913093217custom 52243890319193758232💅1

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

Polls

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.

29 Jul 2026, 11:17 UTCAnonymous Poll128 voters

Как я себя чувствую:

  1. 🔋 Работа хорошая, люди хорошие, у меня всё хорошо15%
  2. 🙂 Есть свои сложности, но в основном всё норм33%
  3. 🫠 Пока держусь, но мозг плавится23%
  4. 🪫 Я давно уже пепел13%
  5. 💀 Я существую только благодаря зарплате16%

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 16 most recent posts we hold, published 8 July 2026 to 5 August 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 3 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.

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

“Вторая линия 💌 поддержка для саппорта” (@sup_2line), 732 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/sup_2line.

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.