BIZTRAC BETA
Buying and selling of own real estate

ERLEND BAKKEN AS

Org. no. 926524895 Limited company (AS) Notodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 115,000
Operating profit NOK 8,000
Equity NOK 4.9m
Incorporated 2020
Share capital NOK 55,000

Signals

1 flags
  • Nylig endring 2026-03-20 Adresseendring registrert 2026-03-20.

ERLEND BAKKEN AS is registered as a limited company in Notodden, Telemark with organisation number 926524895. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 55,000, divided into 55 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av eiendom, investering i selskaper og verdipapirer, og annen virksomhet tilknyttet dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 115,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 115,000
Operating profit
NOK 8,000
Equity
NOK 4.9m
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
-105.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.3%
Very good
Equity as a share of total capital

Who owns ERLEND BAKKEN AS?

ERLEND SELLISETH BAKKEN
ERLEND BAKKEN AS
NOK 115,000 rev. · NOK 8,000 profit

ERLEND BAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERLEND BAKKEN AS own?

ERLEND BAKKEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ERLEND BAKKEN AS

Who owns ERLEND BAKKEN AS?

ERLEND SELLISETH BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of ERLEND BAKKEN AS?

ERLEND BAKKEN AS had revenue of NOK 115,000 in 2024.

Where is ERLEND BAKKEN AS based?

ERLEND BAKKEN AS has its business address in Notodden.

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.