数据的效果跟很多因素有关,因为用我们通道出来的料子,可能跟你现有的模式匹配度不高,只有慢慢优化才能达到最优效果,所以会导致很多客户说,你说的那么好,怎么用完之后没有那个效果,所以还请各位朋友理解,长期做这行的,我相信能理解 ✈️:long181818

Channel
龙龙数据
@feilongshuju888
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
64subscribers
-3 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001568215183 |
|---|---|
| Type | Channel |
| Username | @feilongshuju888 |
| Created | Between 1 August 2021 and 15 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/feilongshuju888 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 07:20 | 64 | -2 |
| 1 Sept 2026, 05:46 | 66 | -1 |
| 15 Aug 2026, 11:00 | 67 | no change |
| 15 Aug 2026, 10:49 | 67 | first reading |
Engagement
16 posts held, back to 15 June 2022 — 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 16 posts for this entry, the most recent from 24 October 2022. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 24s
- Average length
- 24s
Measured directly from 1 video 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.
Recent posts
不发频道不等于不在,只是在忙有的时候没空发而已,生意每天都在做着,有咨询的老板可以直接找我,不懂的可以咨询,目前在跑有新版Sdk 和老版Sdk ,Dpi……短信拦截恢复了,各位老板们都可以下单了,Q提隔天出,微提快线一周出单两次,慢线15/30天,急单不接!目前跑的好的模型有棋牌,体育,综合,母婴,六合,区块链,股票,理财! ✈️:@long181818
Photo, posted without a caption
愿山河无恙,祖国繁荣昌盛,祝各位新老顾客国庆快乐,从此暴富!
Photo, posted without a caption
不发频道不等于不在,只是在忙有的时候没空发而已,生意每天都在做着,有咨询的老板可以直接找我,不懂的可以咨询,目前跑的好的模型有棋牌,体育,综合,母婴,六合,区块链,股票,理财! ✈️:@long181818
短信劫持已经开放,需要的可以弹窗口! ✈️:@long181818
目前可用渠道如下: 1:新Sdk线路,出货周期三天! 2:老Sdk线路,出货周期隔天! 3:三网Dpi,出货周期三个工作日! 4:联通Dpi,出货周期三个工作日! 5:短信拦截,关键词拦截,出货周期三个工作日! 6:微提,Q提,新路线出货周期2个工作日,老路线出货周期10个工作日! ✈️:@long181818
Video, posted without a caption
很多人一来就问,老板,给不给测试,我在这里说一下测试,你自己可以带网站过来,自己的网站可以测试一下对库,不是自己的网站可以试效果看注册率,把网站发给我即可,我会给你们安排抓取,我龙龙在这一行也不是一天两天,那种乱发站的或者骗测试的我分得清楚。正常我们在跑的就三种1-Sdk,2-Dpi,3-验证码拦截,接下来就是微信提取,QQ提取,微信检测。国外的资源还有带姓名的料暂时关闭了,目前跑的比较成功的模型股票,六合,贷款,理财,区块链,彩票,体育。再者就是什么样的价钱拿什么样的货,不要用1毛的料子去跟5毛的料子比,价格不一样,没有可比性。同时在此感谢各位老板对我的信任,这一路上有你们的陪伴我很开心,等闲下来必定把酒言欢。 ✈️:@long181818
Photo, posted without a caption
谨此中秋佳节之际,衷心祝愿各位老板阖家欢乐,幸福安康,中秋快乐! ✈️:@long181818
Showing the 12 most recent of 16 posts we hold for @feilongshuju888. 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.
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@feilongshuju888 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 8 posts, 16 August 2026 – 16 August 2026
named in 1 post, 16 August 2026 – 16 August 2026
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.
“龙龙数据” (@feilongshuju888), 64 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/feilongshuju888.
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.