BIZTRAC BETA
Rental and operating of own or leased real estate

BORGESKOGEN EIENDOMSSELSKAP AS

Org. no. 987509430 Limited company (AS) Sandefjord Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 861,000
Equity NOK 520,000
Incorporated 2004
Share capital NOK 500,000

BORGESKOGEN EIENDOMSSELSKAP AS is registered as a limited company in Sandefjord, Vestfold with organisation number 987509430. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Ervervelse, eie, utvikling og drift av fast eiendom. Videre all annen aktivitet som har naturlig tilknytning til dette, herunder deltakelse og investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 861,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 861,000
Equity
NOK 520,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.0%
Weak
Equity as a share of total capital

Who owns BORGESKOGEN EIENDOMSSELSKAP AS?

JGH INVEST AS
BORGESKOGEN EIENDOMSSELSKAP AS
NOK 1.3m rev. · NOK 861,000 profit

BORGESKOGEN EIENDOMSSELSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BORGESKOGEN EIENDOMSSELSKAP AS

Who owns BORGESKOGEN EIENDOMSSELSKAP AS?

JGH INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BORGESKOGEN EIENDOMSSELSKAP AS?

BORGESKOGEN EIENDOMSSELSKAP AS had revenue of NOK 1.3m in 2025.

Where is BORGESKOGEN EIENDOMSSELSKAP AS based?

BORGESKOGEN EIENDOMSSELSKAP AS has its business address in Stokke.

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.