Telegram RegisterThe public register of Telegram
Telegram profile photo for Invisible Shrimp FAQ

Channel

Invisible Shrimp FAQ

@invisibleshrimpfaq

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

85subscribers

+7 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-1003510530495
TypeChannel
Username@invisibleshrimpfaq
Created17 December 2025measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/invisibleshrimpfaq

Growth

788581.57 August 2026 — 78 subscribers9 August 2026 — 78 subscribers25 August 2026 — 80 subscribers1 September 2026 — 81 subscribers9 September 2026 — 82 subscribers16 September 2026 — 85 subscribers7 August 202616 September 2026
6 measurements spanning 40 days, net +7. 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 77–86 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 18:0085+3
9 Sept 2026, 19:5682+1
1 Sept 2026, 08:3681+1
25 Aug 2026, 02:3780+2
9 Aug 2026, 20:0178no change
7 Aug 2026, 18:4578first reading

Engagement

7 posts held, back to 17 December 2025the 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 7 posts for this entry, the most recent from 7 February 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

56 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 55.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😱3155.4%
1323.2%
🔥916.1%
23.57%
🥰11.79%

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 7 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 56 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 17 December 2025 to 7 February 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

7 Feb 2026, 22:12 UTC≈3,010 views46 reactionsread 9 August 2026
Photo

❔ Для чего нужны ♾️ Infinity профиля в мобильной конфигурации? Предположим, у вас по тарифу моб. оператора закончились гигабайты, но у вас есть безлимит на какой-то сервис (например, ВK), и вам нужно срочно зайти на какой-то сайт который никак не связан с ВК, как раз для таких случаев и пригодится такой тип профилей. 'Blue' [infinity] — если у вас безлимитный 💙 'Pink' [infinity] — если у вас безлимитный 💬 Или прос

😱31🔥752🥰1

29 Jan 2026, 15:25 UTC≈2,810 views0 reactionsread 9 August 2026
Photo

❔ Что делать если на iOS 📱 часто обрывается VPN соединение со стороны ограничений системы? Необходимо включить параметр как на скриншоте, и отключать его если вам не нужен постоянный VPN в системе

25 Jan 2026, 19:29 UTC≈2,620 views6 reactionsread 9 August 2026

📊 Какие ограничения по трафику и устройствам? Ответ: На 🧪 Пробной подписке 5 устройств, 20 ГБ трафика на обычных профилях, мобильные профиля недоступны; На ⭐️ Платной подписке 20 устройств, ♾️ безлимитный трафик на обычных профилях и 10 устройств, 42 ГБ в день на мобильных.

6

17 Jan 2026, 23:25 UTC≈2,470 views0 reactionsread 9 August 2026

❔ В чем разница между №X.1 и №X.2 в обычных профилях? Ответ: Если кратко — №X.1 протокол современнее, но от этого и возникает проблема, что некоторые клиенты (например, на sign-box) пока не работают на нем, как раз для такого случая и существует вариант №X.2. Так же для iOS/iPadOS юзеров лучше использовать как раз таки №X.2 для более стабильной работы соединения (если с первым есть какие-то проблемы) В мобильных ко

22 Dec 2025, 20:37 UTC≈2,490 views2 reactionsread 9 August 2026
Photo

🤔 Как выбрать профиль для подключения? ⚠️ Инструкция устарела, просто используйте профиля на свое усмотрение, но на айфонах лучше использовать X.2 конфиг нужной вам локации. Есть два вида подписки в креветке, обычная подписка, с обычными профилями (Россия, Финляндия, Нидерланды и так далее в будущем), и мобильная, с профилями которые имеют в названии wLTE и которые предназначены для оптимизации мобильного интернета

2

17 Dec 2025, 20:05 UTC≈1,820 views2 reactionsread 9 August 2026

Список вопросов и ответов на них 🍤 1. Как выбрать профиль для подключения 2. Разница между X.1 и X.2 серверами 3. Лимиты по устройствам и трафику 4. Фикс частого вылета VPN на iOS 5. Для чего нужны Infinity профиля

🔥2

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

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.

Named by

Channels on the register whose posts name this channel's handle.

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.

“Invisible Shrimp FAQ” (@invisibleshrimpfaq), 85 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/invisibleshrimpfaq.

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.