To use my script, you need to install Tampermonkey on your browser and then install the script via the link in the first OP.
After that, everything is done automatically. Loading is slow, so you will need to wait a few seconds before you see the results on user profiles.

Thank you very much for letting me know. I'll try to fix it once and for all tonight. I don't want to mess up the tooltip graphics, so I thought I'd do something different: simply refresh by clicking on the BRDb score again, which clears the cache and updates the data. That should work.

EDIT:

I have updated the script to version 0.15.3.
I have reduced the cache memory from 1 hour to 5 minutes.
I have added a button to the profile page to force the data to refresh if corrupted data is displayed. The button is located right next to the brdbscore that you see on the profile page.
Please try it and let me know how it goes.

I have only just noticed this update.
I have already installed it, even though I have never found any incorrect data myself, or at least I have never noticed any corrupted data.
In any case, this button is very useful if incorrect data should arise.
Do you have any other updates in mind?

I am not sure I understood correctly, but you are saying the extension is saving some data locally, not to abuse bitlist.co?
That’s interesting. What happens if you lose the local data? It gets rebuilt on the fly?

Sometimes “nothing broke” is the best test result. Not seeing corrupt scores is already a good sign that the scoring logic and data handling are fairly stable. The reset button feels like one of those features you hope you never need, but you’re glad it exists.
Personally, I'm still trying to figure out the full functionalities of the tool and the reported recent updates from @Ace before I can test run it and probably give my verdict.

It's possible it might be happening with others too. It's just they never noticed it like I did.

Btw, I am not the only person. Remember the last time when I reported, I said LM had the same issue that I noticed? Guess what happened today, when I noticed my faulty data, so did with him also. Same as before. So I don't think it's an only me issue.

As for others, I never paid attention on what they had initially. So I can't separate those ones. I'll let you know if I see this again.

Sorry for the confusion then. I thought it had something to do with your side, I was wrong. Also I have updated the userscript, version 0.15. now, and noticed there is a little refresh button besides the score. It works as I just used it now (again had that miscalculated data a moment ago). So I was wondering is there any way I can help to determine the root cause of this miscalculations? Because it seems like a repeated bug from my end. My browser is updated and only using a few userscripts (2) and extensions (4-5) at this time, which shouldn't cause all this. Is there any log of any kind, that you can take a look or something?

Edit: Forget what I just asked. It seems like too much work. Moreover you have already added a fix to that. So i guess it's pointless digging deeper.  

These are the extensions I currently use. Some of them have been disabled for quite some times now. For example "bitcointalk script". As for BPIP, ShadowPulse and Tampermonkey, these three are always enabled.

Also these are the userscripts I use. As you can see both are from you. So they shouldn't mess with each other.

For now, it'll disable everything (all extensions - not tampermonkey) except "Bitcointalk BRDb score and Bitcointalk usernote" and lets see whether this bug still persistes, fingers crossed.  

Here is the update. The first day, I started using it with everything disabled. Then, from day two, I started enabling one by one (BPIP) and observed after a couple of hours, still normal. On my third day, I turned on SP and that's when I noticed the miscalculation error. Hence, the culprit was ShadowPulse.

The version I used is no longer operational and the latest one hasn't been released yet. So, when it does, maybe you guys can make adjustments, so that both don't have any conflicts. Just a suggestion. That'll be all.

For what it is worth, I updated the extensioncthe other day and everything is working as expected once again.
Wondering what are you preparing for us in the next release.