BIZTRAC BETA
Development of building projects

FROGNER EIENDOM AS

Org. no. 980699978 Limited company (AS) Lillestrøm Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 283,000
Operating profit NOK −369,000
Equity NOK 953,000
Incorporated 1999
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−369k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FROGNER EIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 980699978. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, deltakelse i andre selskaper samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 283,000 in revenue and NOK −369,000 in operating profit.

Key figures · 2024

Revenue
NOK 283,000
Operating profit
NOK −369,000
Equity
NOK 953,000
Est. value
NOK 981,000

Financial health · 2024

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

Who owns FROGNER EIENDOM AS?

ØIE GRUPPEN AS
FROGNER EIENDOM AS
NOK 283,000 rev. · NOK −369,000 profit

FROGNER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER EIENDOM AS

Who owns FROGNER EIENDOM AS?

ØIE GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FROGNER EIENDOM AS?

FROGNER EIENDOM AS had revenue of NOK 283,000 in 2024.

Where is FROGNER EIENDOM AS based?

FROGNER EIENDOM AS has its business address in Lillestrøm.

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.