斯塔迪卡Sw8000 360X4 货架 杆包 路亚救生衣 打包出 联系方式:@Tree9898
❤1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)

Channel
@SeaFishing1
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
142subscribers
-326 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003769617383 |
|---|---|
| Type | Channel |
| Username | @SeaFishing1 |
| Created | Between 1 February 2026 and 8 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 5 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 5 October 2026 |
| On Telegram | t.me/SeaFishing1 |
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 24 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 |
|---|---|---|
| 5 Oct 2026, 20:39 | 142 | -11 |
| 24 Sept 2026, 23:42 | 153 | -71 |
| 13 Sept 2026, 10:17 | 224 | -67 |
| 5 Sept 2026, 12:19 | 291 | -40 |
| 29 Aug 2026, 05:05 | 331 | -56 |
| 21 Aug 2026, 13:15 | 387 | -43 |
| 14 Aug 2026, 23:27 | 430 | -37 |
| 8 Aug 2026, 04:47 | 467 | no change |
| 8 Aug 2026, 00:21 | 467 | -1 |
| 7 Aug 2026, 19:23 | 468 | first reading |
9 posts held, back to 8 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 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 9 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
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.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 👏 | 1 | 50.0% |
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 3 of the 9 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 8 July 2026 to 31 July 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.
斯塔迪卡Sw8000 360X4 货架 杆包 路亚救生衣 打包出 联系方式:@Tree9898
❤1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
粗线不好打结,可以试试这个结 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
🚢【45尺飞鱼号游钓艇】海钓邀约 动力:4台300匹铃木外机,最高航速35节,直达油井钓点180Km,航程3.5小时 载客:限10人以内,可包船、可拼船 📅黄金窗口期:8.1–8.5 连日绝佳海钓天气,窗口期难得 1. 当天往返:5200美金,常规出行凌晨4点出发,下午3点返航。 2. 隔天返航:6200美金 ✅额外:专业导钓 200美金/天 🎣主攻鱼种:巨型石斑、大眼GT、大马鲛、红笛鲷、犁头鳐等深海巨物 有意搏大物钓友抓紧预约占位 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
岸投YYDS😁 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
👏1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
故,单,700? 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
搬运的😂,月底可能会去挑战巨物😍 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
拿到西港来玩肯定爽翻😂 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
明天当岛浪小,有没有老板要包船去当岛,有金枪!
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
🌊🐟 聚友海钓俱乐部 Telegram 频道🔗https://t.me/SeaFishing1
Signed 西港海钓· 杨叙临(借钱请拿枪打我)
Showing the 9 most recent of 9 posts we hold for @SeaFishing1. 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.
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 5 October 2026 — this entry's latest reading, not the date you are reading this.
“聚友海钓俱乐部” (@SeaFishing1), 142 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/SeaFishing1.
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.