VAERS Jun 2, 2023 wrap up!

I plan to do these weekly summary wrap ups for a bit but hopefully it will inspire the reader to jump in and and use the dashboard(s) HERE.

Here is the high level view, notice the distribution by manufacturer looks pretty standard, but the distribution by event level is very high for hospitalization and perm disability.

Also notice the ridiculously high UNKNOWN domestic territory is carrying most of the hospitalizations and good chunk of the DEATHS. For some reason UNK domestic is usually a strong tell the report was throttled (purposely delayed publication).

You see by age that I found 614 -476 = 138 reports where the age was properly documented in the summary narrative section. Disclaimer, for the reports that say the victim was in 40’s, 50’s, 60’s, etc..

I will make them 45,55,65 and play the odds I’m close. Another disclaimer is that many times a victim age is documented as adolescent, teenager, child, baby, neonate, elderly, etc… in these cases I will still put them in the UNK “category” but I populate the age field like this:

So for this drop there were these 38, easily identifiable as such but it’s those 5 kids I want to bring attention too. Now after all this time there are literally thousands of reports hiding in my UNK category that are children, but with one more slice you can zero in on these additional children as well.

Someone please tell the detractors it is possible to “dynamically” scrub the narrative for proper ages. You can vet my work and match against the WYSIWYG resources from within the dashboard as I have dynamically linked to MedAlerts.org.

Maybe I’ll work on multiple dynamic links to OpenVAERS.com and Medalerts.org like matchyourbatch.org successfully does.

Moving on to LOT#’s you can see I have consolidated down 757 to 701 lots. I point out one example at lot# FM9992-PFIZER-2. Not to beat a dead horse, but this is what you get from the bad batch folks:

It’s manageable if you only need to check a couple to a few variations of the same lot#, but when it’s twenty plus different variations it becomes a hot mess!

Here’s a novel idea why don’t all us VAERS folks work together and pool or share a central master file and give the world the best visibility?

I’m game for that, it would be the right thing to do, even if other folks want to jump on stage holding my trophy. Imagine how much more accurate international presentations would be? I digress, moving on…

Let’s get to the brass tacks and the real shimmy-sham. There was eight percent or 194 of 2,430 COVID reports severely throttled reports. Here is what that starts to look like:

This is the visual of lag days between when VAERS received to when they published the report. The other 14 throttled reports which are deaths are reports that supposedly were processed on time by VAERS or at least within the 4-6wk window, but were submitted to VAERS extremely late by the submitter (Manufacturer, hospital, SNF, family member, etc.).

However, let’s start by eyeballing those 25 reports with a lag time of 579 days to publish, doesn’t that stick out sore thumb? Here they are:

2635880, 2635882, 2636491, 2635889, 2635869, 2635884, 2635867, 2635878, 2635877, 2635892, 2636487, 2635873, 2635883, 2635872, 2636570, 2635895, 2635896, 2635888, 2636494, 2635870, 2636574, 2636556, 2636554, 2635885, 2636493

Dar she blows! Please click the ID# and vet yourself, these were all submitted to VAERS on 10/31/2021 and it took VAERS 579 days to let the world know the report existed! Thanks early warning system, you could have at least told us what state they all came from.

Here is a 8 report sample of deaths that took forever to supposedly submit to VAERS? I’m not bothering with the links, I’ll let you guys vet yourselves using openvaers, medalerts, or the wonder system:

In all 39 of 64 “new” deaths (61 percent) were heavily throttled! An additional 5 deaths could not be close to being determined, no doubt in my mind at least a couple of those were probably ancient deaths as well…:

There is so much more to explore but it sure does look like all roads lead to a house of FRAUD!! Pooter, why do I feel like Good Will Hunting? We don’t need no stink’n badges around here, you just bring your A game. God Bless.

OMG! I almost forgot about this Pfizer trial patient?

To many points in the chronological timeline for the vax date to be a typo! This looks legit. I reached out to react19.org on my bat phone, hopefully we can find this lady and figure out when the report was really submitted?

See more here substack.com

Please Donate Below To Support Our Ongoing Work To Expose The Lies About Covid 19

PRINCIPIA SCIENTIFIC INTERNATIONAL, legally registered in the UK as a company incorporated for charitable purposes. Head Office: 27 Old Gloucester Street, London WC1N 3AX. 

Trackback from your site.

Comments (4)

  • Avatar

    Gary Brown

    |

    Apr 28 2023 COVID-19 vaccine injury compilation

    This video highlights some of the most well-documented COVID-19 vaccine injury cases that’ve already been made public on YouTube.

    https://youtu.be/ycx17eQHD1A

    The OpenVAERS Project allows browsing and searching of the reports without the need to compose an advanced search (more advanced searches can be done at medalerts.org or vaers.hhs.gov).

    2,473,400 REPORTS OF VACCINE ADVERSE EVENTS IN VAERS 35,324 COVID Vaccine Reported Deaths / 45,252 Total Reported Deaths 199,790 Total COVID Vaccine Reported Hospitalizations/285,664 Total Reported Hospitalizations 1,556,050 COVID Vaccine Adverse Event Reports Through May 5, 2023

    https://openvaers.com/

    Reply

  • Avatar

    VOWG

    |

    I followed the VAERS numbers until I realized they were just lying. No more following needed.

    Reply

    • Avatar

      VOWG

      |

      I should have mentioned that the lies were understating the truth.

      Reply

  • Avatar

    herb

    |

    Multiple CDC whistleblowers have claimed the CDC has heavily purged VAERS REPORTS from the very beginning .

    To this day under 2% of all deaths and injury’s are reported .

    Reply

Leave a comment

Save my name, email, and website in this browser for the next time I comment.
Share via