biztrac. BETA

Geological surveying in Bergen

The largest companies in geological surveying in bergen, ranked by revenue.

# Company Revenue
1 SHEARWATER GEOSERVICES NORWAY AS org.nr 914633338 · Bergen, Vestland 587.5 mill. kr 2 GEOBIRD MANAGEMENT AS org.nr 982503590 · Bergen, Vestland 338.2 mill. kr 3 GLOBAL SEISMIC SHIPPING AS org.nr 918591664 · Bergen, Vestland 75.2 mill. kr 4 HEAD ENERGY GEO AS org.nr 918585648 · Bergen, Vestland 18.3 mill. kr 5 NEARSHORE SURVEY AS org.nr 912763307 · Bergen, Vestland 8.5 mill. kr 6 SHEARWATER GEOSERVICES AS org.nr 917313415 · Bergen, Vestland 8.4 mill. kr 7 ADEPTH MINERALS AS org.nr 925373044 · Bergen, Vestland 5.0 mill. kr 8 GEOSCAN AS org.nr 998326389 · Bergen, Vestland 863 000 kr 9 NESJE GEO AS org.nr 929487532 · Bergen, Vestland 76 000 kr 10 RESERVOIR INNOVATION AS org.nr 889991062 · Bergen, Vestland 20 000 kr 11 SEISMAPPER AS org.nr 992079169 · Bergen, Vestland – 12 SUBMERSIBLE TECHNOLOGY SERVICES AS org.nr 959558337 · Bergen, Vestland – 13 LONOY GEOCONSULTING AS org.nr 913153170 · Bergen, Vestland – 14 SEISANALYSIS AS org.nr 919788674 · Bergen, Vestland – 15 LJONE AS org.nr 935520959 · Bergen, Vestland – 16 SEI INVEST AS org.nr 989130781 · Bergen, Vestland – 17 SHEARWATER GEOASSETS AS org.nr 923032789 · Bergen, Vestland – 18 TOLLNESET AS org.nr 998245303 · Bergen, Vestland – 19 VISIBLY AS org.nr 927801477 · Bergen, Vestland – 20 SHEARWATER GEOSERVICES HOLDING AS org.nr 917313199 · Bergen, Vestland – 21 ATLANTIC GEODRILL AS org.nr 826769092 · Bergen, Vestland – 22 SHEARWATER GEOSERVICES ASSETS VI AS org.nr 931615319 · Bergen, Vestland – 23 MÅLENE HOLDING AS org.nr 930669652 · Bergen, Vestland – 24 STIKKELINE AS org.nr 830795502 · Bergen, Vestland – 25 WAELA AS org.nr 918305408 · Bergen, Vestland –
Viser 25 av 25 selskaper

This overview shows active companies in the group, ranked by the most recently reported operating revenue. Companies with no filed accounts appear without revenue. The figures are actual registered data from public sources.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.