This read-write value holds the round-trip delay, in milliseconds, that was measured for this trunk at the specific moment it last became operational, serving as a baseline delay figure captured at link-up time rather than continuously updated. An admin compares this baseline against the continuously-refreshed lportTrkDynamicDelay to see how much the trunk's real-time delay has drifted from its original measured condition, which can reveal congestion or a changed physical path. For example, if lportTrkStaticDelay recorded 20ms when the trunk came up but lportTrkDynamicDelay now regularly reads 80ms, that growing gap points to congestion or a routing change degrading the trunk's actual performance since it was last brought up.