BIZTRAC BETA
Rental and operating of own or leased real estate

EIKHAUG AS

Org. no. 916334648 Limited company (AS) Nome Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −27,000
Equity NOK 2.6m
Incorporated 2015
Share capital NOK 2.3m

Signals

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

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

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −27,000
Equity
NOK 2.6m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns EIKHAUG AS?

ARVID TVEITO
EIKHAUG AS
NOK 7,000 rev. · NOK −27,000 profit

EIKHAUG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIKHAUG AS own?

EIKHAUG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIKHAUG AS

Who owns EIKHAUG AS?

ARVID TVEITO is the largest registered owner, with 100.0%.

What is the revenue of EIKHAUG AS?

EIKHAUG AS had revenue of NOK 7,000 in 2025.

Where is EIKHAUG AS based?

EIKHAUG 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.