BIZTRAC BETA
Supply and other sea transport offshore services

EURO INSPECTIONS AS

Org. no. 979921837 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 97,000
Incorporated 1998
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

EURO INSPECTIONS AS is registered as a limited company in Bergen, Vestland with organisation number 979921837. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 1998. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Drive uavhengig service- og konsulentvirksomhet innenfor marine og laste besiktigelser, herunder kvalitetssikring av last, stuasje og rådgivning for handel, industri og forsikring.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK 97,000
Est. value
NOK 103,000

Financial health · 2024

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

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

Who owns EURO INSPECTIONS AS?

NIKOR GROUP AS
EURO INSPECTIONS AS
· NOK −9,000 profit

EURO INSPECTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EURO INSPECTIONS AS

Who owns EURO INSPECTIONS AS?

NIKOR GROUP AS is the largest registered owner, with 100.0%.

Who is the general manager of EURO INSPECTIONS AS?

Karl Erik Presterud is registered as general manager of EURO INSPECTIONS AS.

Where is EURO INSPECTIONS AS based?

EURO INSPECTIONS AS has its business address in Rådal.

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.