BIZTRAC BETA
Rental and operating of own or leased real estate

ÅRVIKI EIENDOM AS

Org. no. 990027994 Limited company (AS) Nome Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 827,000
Equity NOK 3.6m
Incorporated 2006
Share capital NOK 100,000

ÅRVIKI EIENDOM AS is registered as a limited company in Nome, Telemark with organisation number 990027994. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er å eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 827,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 827,000
Equity
NOK 3.6m
Est. value
NOK 4.3m

Financial health · 2025

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

Who owns ÅRVIKI EIENDOM AS?

KNUT OLAF LIA
ÅRVIKI EIENDOM AS
NOK 1.5m rev. · NOK 827,000 profit

ÅRVIKI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅRVIKI EIENDOM AS

Who owns ÅRVIKI EIENDOM AS?

KNUT OLAF LIA is the largest registered owner, with 100.0%.

What is the revenue of ÅRVIKI EIENDOM AS?

ÅRVIKI EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of ÅRVIKI EIENDOM AS?

Knut Olaf Lia is registered as general manager of ÅRVIKI EIENDOM AS.

Where is ÅRVIKI EIENDOM AS based?

ÅRVIKI EIENDOM AS has its business address in Lunde.

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.