BIZTRAC BETA
Business and other management consultancy activities

ERLAND SVEUM AS

Org. no. 926081217 Limited company (AS) Ås Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −34,000
Equity NOK 5.5m
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−34k kr).

ERLAND SVEUM AS is registered as a limited company in Ås, Akershus with organisation number 926081217. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 5.5m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ERLAND SVEUM AS?

ERLAND SVEUM
ERLAND SVEUM AS
NOK 0 rev. · NOK −34,000 profit

ERLAND SVEUM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERLAND SVEUM AS own?

ERLAND SVEUM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ERLAND SVEUM AS

Who owns ERLAND SVEUM AS?

ERLAND SVEUM is the largest registered owner, with 100.0%.

What is the revenue of ERLAND SVEUM AS?

ERLAND SVEUM AS had revenue of NOK 0 in 2025.

Who is the general manager of ERLAND SVEUM AS?

Erland Sveum is registered as general manager of ERLAND SVEUM AS.

Where is ERLAND SVEUM AS based?

ERLAND SVEUM AS has its business address in Vinterbro.

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.