BIZTRAC BETA
Buying and selling of own real estate

BORGESKOGEN 47 AS

Org. no. 913460731 Limited company (AS) Karmøy Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 475,000
Operating profit NOK −771,000
Equity NOK 7.0m
Incorporated 2014
Share capital NOK 364,000

Signals

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

BORGESKOGEN 47 AS is registered as a limited company in Karmøy, Rogaland with organisation number 913460731. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2014. Registered share capital is NOK 364,000, divided into 182000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 475,000 in revenue and NOK −771,000 in operating profit.

Key figures · 2024

Revenue
NOK 475,000
Operating profit
NOK −771,000
Equity
NOK 7.0m
Est. value
NOK 6.4m

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.7%
Good
Equity as a share of total capital

Who owns BORGESKOGEN 47 AS?

JH2 EIENDOM AS
BORGESKOGEN 47 AS
NOK 475,000 rev. · NOK −771,000 profit

BORGESKOGEN 47 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGESKOGEN 47 AS

Who owns BORGESKOGEN 47 AS?

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

What is the revenue of BORGESKOGEN 47 AS?

BORGESKOGEN 47 AS had revenue of NOK 475,000 in 2024.

Where is BORGESKOGEN 47 AS based?

BORGESKOGEN 47 AS has its business address in Karmsund.

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.