Telegram RegisterThe public register of Telegram
Telegram profile photo for InfiniPort Notification Push

Channel

InfiniPort Notification Push

@InfiniPort

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

1,221subscribers

+30 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001502635825
TypeChannel
Username@InfiniPort
CreatedBetween 1 January 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/InfiniPort

Growth

1,1911,2211,2067 August 2026 — 1,191 subscribers7 August 2026 — 1,191 subscribers11 August 2026 — 1,215 subscribers14 August 2026 — 1,221 subscribers7 August 202614 August 2026
4 measurements spanning 7 days, net +30. 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 1,187–1,226 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 04:181,221+6
11 Aug 2026, 01:481,215+24
7 Aug 2026, 06:311,191no change
7 Aug 2026, 06:281,191first reading

Engagement

19 posts held, back to 27 November 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
13.9%
avg views ÷ 1,221 subscribers
Avg views / post
170
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held19 (27 November 20254 August 2026)
Views total170
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 06:31 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.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉834.8%
730.4%
👍626.1%
🦄28.70%

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

Measured over the 19 most recent posts we hold, published 27 November 2025 to 4 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

4 Aug 2026, 16:50 UTC170 viewsread 7 August 2026

#discount 💫 七夕限時優惠 感謝每一位使用者一直以來對 InfiniPort 的支持。 值此七夕之際,我們推出限時優惠活動: 使用優惠碼 QIXI2026,即可享有全站 85 折優惠(15% OFF)。 截止日期:2026 年 8 月 21 日 23:59(UTC+8) 祝大家七夕快樂。

31 May 2026, 17:24 UTC≈1,690 views14 reactionsread 7 August 2026

#discount 🌈 Celebrating Pride Month 2026 支持多元、包容與開放的網際網路。 使用優惠碼 PRIDE2026,即可享有全站 9 折優惠(10% OFF)。 截止日期:2026 年 6 月 30 日(UTC+8)

🎉84🦄2

31 May 2026, 10:20 UTC≈1,310 views4 reactionsread 7 August 2026
Photo

#update 現在可以在官網上查看節點狀態了。 您可於用戶中心的 「節點狀態 Beta」 頁面查看各地區節點的即時運行情況,包含: * 節點延遲 * 穩定性狀態 * 近期探測記錄 由於功能仍處於 Beta 測試階段,探測結果僅供參考,我們也將持續優化監測準確度與功能體驗。

👍4

30 May 2026, 11:10 UTC956 views2 reactionsread 7 August 2026
Photo

#update 現在可以在官網上查詢當月流量明細了。

👍2

21 May 2026, 03:40 UTC343 viewsread 7 August 2026
Forwarded from @QuanXNews

Quantumult X for iOS/tvOS/macOS 正式版更新 1.5.6 商店链接 更新时间: 2026-05-21 更新说明: - Add support for AnyTLS proxy protocol. - Bug fixes and other minor improvements. 其他: - 更新订阅失败的解决办法 - 节点标识说明 群组: @QuanXApp 频道: @QuanXNews

4 May 2026, 05:27 UTC≈1,340 views2 reactionsread 7 August 2026

#node 節點恢復通知 因有用戶反饋仍需要 🇦🇷 AR 01 節點,該節點現已恢復上線。 若您有其他地區或節點需求,歡迎於此貼下方回覆,我們將視實際需求進行評估與調整。 感謝您的理解與支持。

2

1 May 2026, 10:53 UTC≈1,280 viewsread 7 August 2026

#node 節點下線通知及需求收集 由於 🇦🇷 AR 01 節點長期處於低使用率狀態,現已下線。 若您有其他地區或節點需求,歡迎於此貼下方回覆,我們將視實際需求進行評估與調整。 感謝您的理解與支持。

29 Apr 2026, 12:38 UTC≈1,280 viewsread 7 August 2026

#announcement (目前尚未確認消息來源與真實性,本提醒僅為降低可能風險) 關於網路環境使用建議的通知 如您身處中國大陸地區,且正在使用校園網路,建議您盡量改於非校園網路環境下使用。部分院校可能會對相關使用行為進行監測或封鎖。 如您身处中国大陆地区,且正在使用校园网路,建议您尽量改于非校园网路环境下使用。部分院校可能会对相关使用行为进行监测或封锁。 該資訊為網路流傳消息。為盡可能保障您的權益,特此提醒。

13 Apr 2026, 16:27 UTC≈1,640 views1 reactionsread 7 August 2026

#announcement 關於客戶端使用建議的通知 如您在使用過程中遇到任何問題,請先嘗試更新或更換客戶端進行排查。 iOS 端建議使用 Shadowrocket; Android 端建議使用 FlClash; Windows、macOS 建議使用 Clash Verge Rev。 使用文檔將於稍後更新。 如更換後問題仍未解決,請再進一步反饋。

1

2 Apr 2026, 23:02 UTC≈1,910 views0 reactionsread 7 August 2026

#announcement 因不可抗力因素影響,本站中國大陸地區線路曾出現連線異常,目前已部分恢復,但仍處於觀察階段,可能存在不穩定情況。 對此帶來的不便深表歉意,感謝您的理解與支持。

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

Citation-graph rank

Citation-graph rank — 863,666 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

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.

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

“InfiniPort Notification Push” (@InfiniPort), 1,221 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/InfiniPort.

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.