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

MILJETEIG EIENDOM AS

Org. no. 980601722 Limited company (AS) Ullensaker Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 597,000
Equity NOK 7.6m
Incorporated 1999
Share capital NOK 2.0m

MILJETEIG EIENDOM AS is registered as a limited company in Ullensaker, Akershus with organisation number 980601722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 2.0m, divided into 100 shares. The company's stated purpose is: “Utleie av fast eiendom samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 597,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 597,000
Equity
NOK 7.6m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns MILJETEIG EIENDOM AS?

MILJETEIG EIENDOM AS
NOK 2.0m rev. · NOK 597,000 profit

MILJETEIG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MILJETEIG EIENDOM AS

Who owns MILJETEIG EIENDOM AS?

IVAR CHRISTOFFER MILJETEIG is the largest registered owner, with 100.0%.

What is the revenue of MILJETEIG EIENDOM AS?

MILJETEIG EIENDOM AS had revenue of NOK 2.0m in 2025.

Who is the general manager of MILJETEIG EIENDOM AS?

Ivar Christoffer Miljeteig is registered as general manager of MILJETEIG EIENDOM AS.

Where is MILJETEIG EIENDOM AS based?

MILJETEIG EIENDOM AS has its business address in Kløfta.

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

Report a problem

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