Kano 手記
@kano06Tracked since May 2026
creating Investment Ideas.
How Patreon Signal reads this profile
Identity, tiers, posts, and visible counts come from the latest public Patreon observation. Growth compares available public snapshots. Revenue is labeled observed only when Patreon exposes it; otherwise it is modeled from public membership and tier signals.
HKD 5.6K–6.2K modeled range
Pricing and benefits captured publicly
Patreon is not exposing patron counts by tier for this creator, so this section shows public prices and benefits only.
70 paid members · past 30 days
The chart only uses Kano 手記's observed public history. Comparison peers are listed below, but comparable trend series are not available yet.
Where Kano 手記 ranks
A focused cohort chosen from content relevance, category, audience, pricing, and cadence. Changing the rank metric does not change who belongs in this cohort.
7 of 9 cohort creators have a measured total audience; the other 2 remain unranked for this metric.Ranking data · includes stale rows| Rank | Creator and why included | Total audience | Gap vs Kano 手記 | Freshness |
|---|---|---|---|---|
| #2 |  Fitzo CryptoWritingCategory, audience, pricing & cadence | 769 | 464 more | Aug 2, 2026 |
| #3 |  落雨人WritingContent relevance + business context | 338 | 33 more | Aug 5, 2026 |
| #4 | Kano 手記ProfileWritingTotal audience position in Recommended cohort | 305 | Reference | Aug 2, 2026Stale |
| #5 |  Cloudharry - 牛奶投資教育小組MusicContent relevance + business context | 48 | 257 fewer | Aug 2, 2026 |
| #6 |  algo工作坊WritingContent relevance + business context | 42 | 263 fewer | Jul 22, 2026Stale |
The rank uses the full fixed cohort. This table shows up to five creators around Kano 手記; the coverage summary above still counts everyone.
Recent posts
Previews available for 25 of 70 posts
Article Latest post$80 tier & up螢幕截圖 2024-07-22 上午12.15.47.png一打 「雷達」 就諗起 Gundam X 又時童年回憶。 因為太耐無打 雷達， 同上次相比有大執位。 ...
Jul 21, 2024 18 likes 29 commentsKeep Kano 手記 in context.
Save the creator, add them to a comparison, or return to the exact Explore view you came from.