BIZTRAC BETA
Rental and operating of own or leased real estate

TENDEN EIGEDOM AS

Org. no. 923168419 Limited company (AS) Stryn Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.5m
Equity NOK 4.9m
Incorporated 2019
Share capital NOK 500,000

TENDEN EIGEDOM AS is registered as a limited company in Stryn, Vestland with organisation number 923168419. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Eie og forvalte eigedom og tjenester/produkter som naturlig faller sammen med dette, herunder delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.5m
Equity
NOK 4.9m
Est. value
NOK 4.8m

Financial health · 2024

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

Who owns TENDEN EIGEDOM AS?

PEOS INVEST AS
TENDEN EIGEDOM AS
NOK 2.7m rev. · NOK 1.5m profit

TENDEN EIGEDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does TENDEN EIGEDOM AS own?

TENDEN EIGEDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TENDEN EIGEDOM AS

Who owns TENDEN EIGEDOM AS?

PEOS INVEST AS is the largest registered owner, with 40.0%.

What is the revenue of TENDEN EIGEDOM AS?

TENDEN EIGEDOM AS had revenue of NOK 2.7m in 2024.

Where is TENDEN EIGEDOM AS based?

TENDEN EIGEDOM AS has its business address in Stryn.

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.