BIZTRAC BETA
Rental and operating of own or leased real estate

OLDERNESET UTLEIEBYGG AS

Org. no. 976030842 Limited company (AS) Hemnes Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 655,000
Operating profit NOK 153,000
Equity NOK 1.4m
Incorporated 1995
Share capital NOK 1.0m

OLDERNESET UTLEIEBYGG AS is registered as a limited company in Hemnes, Nordland with organisation number 976030842. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1995. Registered share capital is NOK 1.0m, divided into 417 shares. The company's stated purpose is: “Utleie, samt hva herved står i forbindelse. Selskapet kan også delta i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 655,000 in revenue and NOK 153,000 in operating profit.

Key figures · 2025

Revenue
NOK 655,000
Operating profit
NOK 153,000
Equity
NOK 1.4m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns OLDERNESET UTLEIEBYGG AS?

SNORRE KRISTIANSEN
OLDERNESET UTLEIEBYGG AS
NOK 655,000 rev. · NOK 153,000 profit

OLDERNESET UTLEIEBYGG AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does OLDERNESET UTLEIEBYGG AS own?

OLDERNESET UTLEIEBYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLDERNESET UTLEIEBYGG AS

Who owns OLDERNESET UTLEIEBYGG AS?

SNORRE KRISTIANSEN is the largest registered owner, with 7.7%.

What is the revenue of OLDERNESET UTLEIEBYGG AS?

OLDERNESET UTLEIEBYGG AS had revenue of NOK 655,000 in 2025.

Where is OLDERNESET UTLEIEBYGG AS based?

OLDERNESET UTLEIEBYGG AS has its business address in Korgen.

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.