I don't wish to jump to the conclusion that the tag is not well implemented.
But perhaps it is being triggered on a different page, because that is the only page where User Tpe = Premium is available.
Then, thanks to the persistence of eVars (and this is highly dependent on how the eVar is configured) the 'Premium' value follows you around, so that you can run a report showing the number of Premium users logged in.
But like Arun said, User Type may also be set via other methods, such as Processing Rules, Data Sources, Vista Rules, or even Classifications. You could ask your architect for this information, or failing that, the original Solution Design (Plan B).
Plan C would be to find out if your analytics account has Web API access so you could try to produce your own Solution Design using the excellent ObservePoint Labs - G Suite Marketplace addon for Google Sheets.
this "addon" to your analytics implementation tracks the props/evars/events you have in a single server call.
for similar use cases such as written in the question, I could just search for my desired eVar, breakdown by page to see where it has been set. or breakdown by any other dimension which might affect my data collection
Reason 1: The URL/condition validating is not correct.
To understand where the eVar101 is firing, create a segmentation with 'Hit' container equals the value you see in eVar101. It will show only the pages where the eVar101 has value. Try to load the page and see if you are able to see eVar101 in the debugger.
If you are using DTM or Launch, verify how eVar101 was implemented within the tools. That will give you a brief idea on where and on which condition eVar101 is firing if it is done at the tool level. Else, the only option is Processing Rules.
Reason 2: Check the Processing Rules.
There are chances that your Architect would have opted for Processing Rules to set eVar101 rather than firing at the pages. So, check Processing Rules.
Reason 3 : Data Source
If eVar101 was imported into Adobe Analytics using Data Source, you would not see the variables both at the page level or Processing Rules. Check with your Architect to understand the data import.
Aside, make sure that the above said name is not a Classification Variable Name.
One way I have found to start working out where an eVar was set it to build a table in Adobe Workspace with custom link name or page in the left column, and the eVar instances metric, visits, and occurences along the top. (Tip, pick a short date range like Yesterday, or Last 7 days)
Custom Link Name
UserType (C101) Instances
link name 1
link name 2
link name 3
User Type (C101) Instances
UserType (C101) Instances
The dummy tables above would lead me to check whether eVar101 is set on the Dashboard page, or on custom link name 2.