BIZTRAC BETA
COMPANY REGISTER PROFILE
912156478 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

N L AUSTNES EIGEDOM AS

Org. no. 912156478 Limited company (AS) Haram Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 360,000
Operating profit NOK 220,000
Equity NOK 30,000
Incorporated 2013
Share capital NOK 30,000

N L AUSTNES EIGEDOM AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 912156478. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er: Utleie av fast eiendom, samt virksomhet som hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 360,000 in revenue and NOK 220,000 in operating profit.

Key figures · 2025

Revenue
NOK 360,000
▲ +10 %
Operating profit
NOK 220,000
▲ +14 %
Equity
NOK 30,000
▲ +0 %
Est. value
NOK 491,000

Financial health · 2025

Liquidity
3.84
Very good
Current assets ÷ current liabilities
Profitability
12.6%
Good
Return on total assets
Solidity
2.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns N L AUSTNES EIGEDOM AS?

N L AUSTNES EIGEDOM AS
NOK 360,000 rev. · NOK 220,000 profit

N L AUSTNES EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about N L AUSTNES EIGEDOM AS

Who owns N L AUSTNES EIGEDOM AS?

N L AUSTNES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of N L AUSTNES EIGEDOM AS?

N L AUSTNES EIGEDOM AS had revenue of NOK 360,000 in 2025.

Where is N L AUSTNES EIGEDOM AS based?

N L AUSTNES EIGEDOM AS has its business address in Haramsøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.