A Common Operational Picture (COP) assistant for KanColle.
Users
8
+2 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#216K
#181K among extensions
Version
1.1.0.7
updated 17 Oct 2026
Users
monthly, 3 months
Latest, 20 Oct 2026:8 usersMove the mouse over the chart for any month
Ratings count
monthly, 3 months
Latest, 20 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Fleet Chronometer - KanColle COP
https://github.com/Hian201/fleet-chronometer
This is a fan-made companion tool. It is not affiliated with, endorsed by, or sponsored by DMM.com or Kadokawa Games. "KanColle" and all game assets belong to their respective owners.
Do not treat this extension's displays or predictions as your only source of truth. Back up anything that matters.
Features
• Live panel — fleet HP/fatigue/supply, expedition & docking countdowns (with notifications), base air corps, map gauge progress.
• Battle prediction — end-of-battle HP, rank, MVP, and heavy-damage warnings from the packets the game already sends you.
• Fuel/ammo estimation — per-node estimates mid-sortie, corrected on return to port.
• Sortie log — one card per sortie: route, formation, per-node combat, support / base air corps waves; exportable as KC3Kai battleplayer replay.
• Resource log — one multi-line chart for all eight materials, with per-event-stage consumption.
• Event operations board — tracks sally-tag rules so you don't lock a ship into the wrong route.
• Fleet & equipment roster — filterable/sortable inventory.
• Local backups — export/import to a folder you choose, with an offline HTML viewer.
• Fit to Window — fit the game canvas to the browser window; mute audio.
Privacy & safety
• Passive capture only — observes traffic the game already sends; never replays, modifies, or sends requests on your behalf.
• No account credentials leave your browser — api_token is stripped before storage or internal broadcast and is never persisted.
• Nothing is uploaded — all data stays in local IndexedDB; there is no backend.
• Minimal permissions — requested only when a feature needs them (e.g. Fit to Window asks for the DMM game page only when you click the button — never on install).