biztrac. BETA
COMPANY REGISTER PROFILE
990633258 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Auditing

STORBOTN NÆRING AS

Org. no. 990633258 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −109,000
Equity NOK 27.4m
Incorporated 2006
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−109k kr).
  • Nylig endring 2026-09-02 Aksjekapital registrert 2026-09-02.

STORBOTN NÆRING AS is registered as a limited company in Bergen, Vestland with organisation number 990633258. The business is classified under auditing (NACE 69.201). The company was incorporated in 2006. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Investering i og drift av fast eiendom, tjenester innenfor revisjon, regnskapsføring og økonomisk rådgivning, samt investering i aksjer i selskap med tilsvarende formål.”.

Former names: REVISORPARTNER AS

Key figures · 2025

Operating profit
NOK −109,000
▲ +2 %
Equity
NOK 27.4m
▲ +6 %
Est. value
NOK 36.5m

Financial health · 2025

Liquidity
3.05
Very good
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
68.2%
Very good
Equity as a share of total capital

Who owns STORBOTN NÆRING AS?

STORBOTN NÆRING AS
· NOK −109,000 profit

STORBOTN NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STORBOTN NÆRING AS own?

STORBOTN NÆRING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about STORBOTN NÆRING AS

Who owns STORBOTN NÆRING AS?

Aage Sundal is the largest registered owner, with 100.0%.

Who is the general manager of STORBOTN NÆRING AS?

Aage Sundal is registered as general manager of STORBOTN NÆRING AS.

Where is STORBOTN NÆRING AS based?

STORBOTN NÆRING 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 03.10.2026.

Report a problem

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