@Egbejiogu,
As always, @Harsh is absolutely spot on. Your incorrect results could be due to: problems with your [Mobility] measure; problems with the context in which you’re applying it; and/or problems with your data model. Without seeing your PBIX file it’s impossible to tell which one is the culprit.
In addition, I noticed something in your earlier post – a misinterpretation of the CALCULATE function. I think CALCULATE gives so many people trouble not because it’s that difficult, but because it is so poorly named. CALCULATE actually has little to do with calculations directly, but instead changes the context of the calculation occurring. Thus, whenever I see CALCULATE, I mentally have trained myself to substitute CHANGECONTEXT() (a function that doesn’t actually exist, but should - in the same way that REMOVEFILTERS can be used synonymously with ALL (in some cases…), but is much clearer as to what it is doing).
In your case above of CALCULATE(100), no context is being changed so CALCULATE isn’t doing anything, which is why Harsh removed it (also because CALCULATE on a constant doesn’t do anything either). Sam has a whole series of outstanding videos on CALCULATE in the Mastering DAX course:

Understanding context and the way CALCULATE can be used to manipulate it is probably THE key concept necessary to write proper DAX.
I hope this is helpful.