BIZTRAC BETA
Geological surveying

NEARSHORE SURVEY AS

Org. no. 912763307 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 604,000
Equity NOK 3.1m
Incorporated 2013
Employees 7
Share capital NOK 30,000

NEARSHORE SURVEY AS is registered as a limited company in Bergen, Vestland with organisation number 912763307. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2013 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppmåling og kartlegging i sjø og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 604,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 604,000
Equity
NOK 3.1m
Est. value
NOK 4.4m

Financial health · 2024

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
45.4%
Very good
Equity as a share of total capital

Who owns NEARSHORE SURVEY AS?

HALVOR MOHN
NEARSHORE SURVEY AS
NOK 8.5m rev. · NOK 604,000 profit

NEARSHORE SURVEY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEARSHORE SURVEY AS

Who owns NEARSHORE SURVEY AS?

HALVOR MOHN is the largest registered owner, with 100.0%.

What is the revenue of NEARSHORE SURVEY AS?

NEARSHORE SURVEY AS had revenue of NOK 8.5m in 2024.

Who is the general manager of NEARSHORE SURVEY AS?

Halvor Mohn is registered as general manager of NEARSHORE SURVEY AS.

Where is NEARSHORE SURVEY AS based?

NEARSHORE SURVEY AS has its business address in Øvre Ervik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

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