biztrac. BETA
COMPANY REGISTER PROFILE
915236960 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

TOTEN EIENDOMSUTVIKLING AS

Org. no. 915236960 Limited company (AS) Østre Toten Incorporated 2015 Active
Operating profit NOK −18,000
Equity NOK 1.4m
Incorporated 2015
Share capital NOK 100,000

Signals

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

TOTEN EIENDOMSUTVIKLING AS is registered as a limited company in Østre Toten, Innlandet with organisation number 915236960. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, oppføring, utleie og drift av fast eiendom samt alt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −18,000
▲ +7 %
Equity
NOK 1.4m
▲ +22 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
2490.00
Very good
Current assets ÷ current liabilities
Profitability
14.0%
Good
Return on total assets
Solidity
64.2%
Very good
Equity as a share of total capital

Who owns TOTEN EIENDOMSUTVIKLING AS?

TOTEN EIENDOMSUTVIKLING AS
· NOK −18,000 profit

TOTEN EIENDOMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TOTEN EIENDOMSUTVIKLING AS own?

TOTEN EIENDOMSUTVIKLING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TOTEN EIENDOMSUTVIKLING AS

Who owns TOTEN EIENDOMSUTVIKLING AS?

KMP HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of TOTEN EIENDOMSUTVIKLING AS?

Per Even Ulsrud is registered as general manager of TOTEN EIENDOMSUTVIKLING AS.

Where is TOTEN EIENDOMSUTVIKLING AS based?

TOTEN EIENDOMSUTVIKLING AS has its business address in Skreia.

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.