BIZTRAC BETA
Rental and operating of own or leased real estate

FROGNER HOVEDGÅRD AS

Org. no. 927342782 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK 2.5m
Equity NOK 1.7m
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FROGNER HOVEDGÅRD AS is registered as a limited company in Skien, Telemark with organisation number 927342782. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forvalte Frogner Hovedgård.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK 2.5m
Equity
NOK 1.7m
Est. value
NOK 6.4m

Financial health · 2024

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.4%
Satisfactory
Equity as a share of total capital

Who owns FROGNER HOVEDGÅRD AS?

KRISTIANIA EIENDOM AS
FROGNER HOVEDGÅRD AS
NOK 6.0m rev. · NOK 2.5m profit

FROGNER HOVEDGÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FROGNER HOVEDGÅRD AS

Who owns FROGNER HOVEDGÅRD AS?

KRISTIANIA EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FROGNER HOVEDGÅRD AS?

FROGNER HOVEDGÅRD AS had revenue of NOK 6.0m in 2024.

Who is the general manager of FROGNER HOVEDGÅRD AS?

John Kristianslund is registered as general manager of FROGNER HOVEDGÅRD AS.

Where is FROGNER HOVEDGÅRD AS based?

FROGNER HOVEDGÅRD AS has its business address in Skien.

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.