Real world drops and Shooter app vastly different. 6.5 Saum, 156 EOL Bergers, RL26

[pwrdbycotn]

Today I took my 6.5 saum out to get ready for deer season. Since last season I have changed scopes (Tangent Theta 315P) and decided to switch to the 156gr EOL bullets.
I am loading 58 gr RL-26, 215M, ADG brass with no signs of pressure.
According to my labradar, my speeds were as follows: 2990, 3014, 3018, 3022, 3018, 3022, 3025, 3024, 3030, 3025, 3026, 3027, 3021, 3025, 3032, 3024, 3038, 3014, 3021, 3034, 3040, 3027, 3040, 3037, 3052
Rounds were left in the sun in the ammo box, which is why the speeds climbed some over the course of 2.5 hrs.
The gun wears a suppressor made by Hog Rush.
This load shoots very well accuracy-wise.

Here's the issue:
My shooting confirmed my drops as follows
200 yd- zero
400 yd- 5.25 moa
600 yd- 11.25
800 yd- 16.25
The shooter app calls for:
400 yd- 3.0
600 yd- 8.0
800 yd- 13.8

Why is there such a big difference? I've used the Shooter app for years and while there has always been a slight discrepancy between the real world and the app, it has always been minor and I've been able to make everything match up with minor velocity adjustments in the app.
Scope tracking shows to be spot on, and I am making certain there are no canting issues.
I plan to shoot again before season just to verify drops again.

Edit to add: 350 ft ASL, 31% humidity today, 68*
Gun is custom built by Pierce Engineering, 26" Brux, Pierce ti action, Manners, Jewell, Atlas bipod,

What gives?

 

[pawater]

G1 vs g7 bc? Zero data in app? Correction factor in app? It has to be an entry to be that far off.

 

[pwrdbycotn]

G1 vs g7 bc? Zero data in app? Correction factor in app? It has to be an entry to be that far off.

I tried both the G7 and the G1 with very minor difference. I have double checked everything.

 

[LongBomber]

As long as all your inputs are correct in the program, I would look at the scope.

 

[pawater]

I plugged it in applied ballistics. Shows 14.5 to 800

 

[pawater]

What velocity did you use?

 

[pwrdbycotn]

As long as all your inputs are correct in the program, I would look at the scope.

I tested the tracking and it's spot on as far as a box test at 100 yards. Windage at distance was correct and minor correction at each interval were correct as well.

What velocity did you use?

I am using 3025

 

[pawater]

Any wind involved? Did you run the labradar while confirming? I've seen weird things when the barrel is screaming I want cleaned. Some more often than others. I haven't shot much rl26 to know the characteristics.

 

[pwrdbycotn]

Any wind involved?

3-5 mph from 280ish*. Shooting straight north and the wind was west/northwest, but not much of a factor.

 

[whatnext]

Did you change the FPS or did you enter your actual drops in the truing function?

 

[pwrdbycotn]

In the velocity calibration, it tries to say true velocity is 2760. If I change that in the bullet edit, it still calls for less drop than I experienced today.

 

[LaHunter]

Double check the units that are active on your app. The app is way off of reality, not even close. You would have to be shooting a lazer based on those solutions.

 

[whatnext]

Go here and enter actual drops. Your trying to resolve a ballistic curve by guessing at the velocity which may not be the issue. It could be environmental or BC.

 

[whatnext]

The more real drops you enter the better it can resolve the curve. I will say this, I don't like it because garbage in -garbage out. I've experienced the same problem but when you can't identify the error, it's the next best thing I know to do. Just be sure to enter drops sequentially from short to long