mystery_sightings seems too much fed

[NicoDeVang]

My "mystery_sightings" table has 13 rows, as "sightings" only 2. Do you know what it could mean?

There is my last scan:

Monocle running for 0:11:43.844784
Known spawns: 0, unknown: 6, more: 0
1 workers, 32 coroutines
sightings cache: 0, mystery cache: 2, DB queue: 0

Seen per worker: min 3, max 3, med 3
Visits per worker: min 5, max 5, med 5
Visit delay: min 0.0, max 0.0, med 0.0
Speed: min 11.9, max 11.9, med 11.9
Extra accounts: 0, CAPTCHAs needed: 0

Pokemon found count (10s interval):
2 2 2 2 2 2 2 2 2

Visits: 5, per second: 0.01
Skipped: 0, unnecessary: 0
Seen per visit: 0.60, per minute: 0
Hashes: 149/150, refresh in -64

By the way, my "hashes remaining" always are at 149 (as we can see here) or sometimes 148 but at worse 146, as in the config file my SCAN_DELAY = 1 so I don't understand why it only uses one "hash" and not like 60 in a minute? And why the refresh is negative? (-64 here, and sometimes it comes back to 60 but it's rare)

Any help should be amazing :)

[DavePlater]

If you have changed your map location (MAP_START or MAP_END) without flushing our your DB, you will have stale entries in there?