BIZTRAC BETA
Civil engineering activities

ERIKSEN HAZMAT SURVEY NORD AS

Org. no. 931655213 Limited company (AS) Bodø Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 83,000
Incorporated 2023
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

ERIKSEN HAZMAT SURVEY NORD AS is registered as a limited company in Bodø, Nordland with organisation number 931655213. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Byggeteknisk konsulentvirksomhet, og hva hermed står i forbindelse, samt deltakelse i andre forretningsforetak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 83,000
Est. value
NOK 135,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ERIKSEN HAZMAT SURVEY NORD AS?

ERIKSEN HMS AS
ERIKSEN HAZMAT SURVEY NORD AS
NOK 0 rev. · NOK −10,000 profit

ERIKSEN HAZMAT SURVEY NORD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ERIKSEN HAZMAT SURVEY NORD AS

Who owns ERIKSEN HAZMAT SURVEY NORD AS?

ERIKSEN HMS AS is the largest registered owner, with 60.0%.

What is the revenue of ERIKSEN HAZMAT SURVEY NORD AS?

ERIKSEN HAZMAT SURVEY NORD AS had revenue of NOK 0 in 2024.

Where is ERIKSEN HAZMAT SURVEY NORD AS based?

ERIKSEN HAZMAT SURVEY NORD AS has its business address in Bodø.

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.