Telegram RegisterThe public register of Telegram
Telegram profile photo for 론 디비

Channel

론 디비

@LOAN_CHANNEL1

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

106subscribers

+2 since we began measuring on 3 November 2026

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

Register entry

Telegram ID-1003914404564
TypeChannel
Username@LOAN_CHANNEL1
CreatedBetween 1 April 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 November 2026
Last confirmed live4 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/LOAN_CHANNEL1

Growth

1041061053 Nov 2026, 17:22 — 104 subscribers4 Nov 2026, 07:07 — 106 subscribers3 Nov 2026, 17:224 Nov 2026, 07:07
2 measurements taken within a single day, net +2. 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 104–106 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 07:07106+2
3 Nov 2026, 17:22104first reading

Engagement

14 posts held, back to 31 October 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.

ERR · 30 days
102.0%
avg views ÷ 106 subscribers
Avg views / post
108
14 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
14
of 14 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 3 November 2026
Posts held14 (31 October 2026 – 3 November 2026)
Views total1,513
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Nov 2026, 17:22 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.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 14 posts held from the last 30 days (7.14%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

3 Nov 2026, 10:51 UTC20 viewsread 3 November 2026

⚠️ 오늘 하루도 고생 많으셨습니다 !⚠️ 🔻 실시간 대출 DB 단독 T.O ✔️ 예약 바로 가능합니다 ! 문의주세요 ! ⚠️ 한자리 있습니다 ⚠️ 🔥🔥🔥 😀 @LOAN_DB

3 Nov 2026, 02:06 UTC45 viewsread 3 November 2026

🔥🔥🔥🔥🔥🔥🔥🔥 🔻 실시간 대출 DB 단독 T.O 🍳 전일 DB 🍳 이월 DB 🍳 승인DB 🍳 문발 DB ✔️ 진행 바로 가능합니다 ! 문의주세요 ! 🔥🔥🔥 😀 @LOAN_DB 🔥🔥🔥 😀 @LOAN_CHANNEL1 🔥🔥🔥🔥🔥🔥🔥🔥🔥

2 Nov 2026, 17:24 UTC57 viewsread 3 November 2026
Photo

⚠️ 사칭 주의 ⚠️ ⚠️ 디비를 구매 한다고 하여서 ⚠️ 마감하고도 열심히 하나하나 타이핑 하여 일부 완성하고 취침 준비 중 중개거래 비용 입금했으면 제대로 당할 뻔 했습니다. ⚠️ 항상 방장이나 관리자 사칭, ⚠️ 뒷텔 및 삼자방연결 이 부분 조심하시길 바랍니다. 시간 낭비 정말 싫어하는데, 어쩐지 판매자가 중개거래 비용을 같이 넣는것 자체가 수상하긴 했습니다. 덕분에 고생 많이 했습니다. 하하 📌 특히나 바쁜 마감 시간에 📌 더더욱 유의하시길 바랍니다. 편안한 밤 되십시요. 감사합니다 !

2 Nov 2026, 13:32 UTC61 viewsread 3 November 2026

⚠️ 오늘 하루도 고생 많으셨습니다 !⚠️ 🔻 실시간 대출 DB 단독 T.O ✔️ 예약 바로 가능합니다 ! 문의주세요 ! ⚠️ 한자리 있습니다 ⚠️ 오늘 예약건들 준비하느라 밤새야 합니다😂 🔥🔥🔥 😀 @LOAN_DB

1 Nov 2026, 23:59 UTC73 viewsread 3 November 2026

⚠️ 좋은아침 입니다 !⚠️ 🔻 실시간 대출 DB 단독 T.O ✔️ 진행 바로 가능합니다 ! 문의주세요 ! 🔥🔥🔥 😀 @LOAN_DB

1 Nov 2026, 11:34 UTC86 viewsread 3 November 2026

⚠️ 오늘 하루도 고생 많으셨습니다 !⚠️ 🔻 실시간 대출 DB 단독 T.O ✔️ 예약 바로 가능합니다 ! 문의주세요 ! ⚠️ 한자리 있습니다 ⚠️ 🔥🔥🔥 😀 @LOAN_DB

1 Nov 2026, 11:04 UTC85 viewsread 3 November 2026
Photo

⚠️ 11월 1일 주결제 단독 T.O 대표님 ⚠️ 짧은 소통 이후 현재 타 업체를 이용 중이심에도 불구하고, 최소 수량이라도 먼저 받아보시겠다는 대표님. 소중한 시간과 기회가 헛되지 않도록 좋은 결과로 보답할 수 있게 최선을 다해 송부드리겠습니다. 믿고 기회 주셔서 진심으로 감사드립니다. 🔥🔥🔥🔥🔥🔥 🔥🔥🔥 😀 @LOAN_DB 🔥🔥🔥🔥🔥🔥🔥🔥🔥

1 Nov 2026, 03:01 UTC92 viewsread 3 November 2026
Video

⚠️ 다가오는 월요일 ! ⚠️ 🔻 실시간 대출 DB 단독 T.O ✔️ 예약 바로 가능합니다 ! 문의주세요 ! 🍳 11월 성업하십시요 ! 🍳 🔥🔥🔥 😀 @LOAN_DB

31 Oct 2026, 16:39 UTC91 viewsread 3 November 2026

⚠️ 대표님들께 전달드립니다 ⚠️ 지난 10월 제휴를 맺고 홍보에 힘을 보태주시며 함께하게 된 각 방 대표님들께 진심으로 감사드립니다. 11월에는 모든 대표님들의 사업이 더욱 번창하고, 하시는 일마다 좋은 결실을 맺으시기를 간절히 기원하겠습니다. 늘 힘 실어주셔서 다시 한번 감사드립니다 ! 🤣

Showing the 12 most recent of 14 posts we hold for @LOAN_CHANNEL1. 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 4 November 2026 — this entry's latest reading, not the date you are reading this.

“론 디비” (@LOAN_CHANNEL1), 106 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/LOAN_CHANNEL1.

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.