BIZTRAC BETA
Development of building projects

DRONNINGENSGATE 39 AS

Org. no. 923306129 Limited company (AS) Fredrikstad Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 891,000
Operating profit NOK 585,000
Equity NOK −579,000
Incorporated 2019
Share capital NOK 31,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−579k kr).

DRONNINGENSGATE 39 AS is registered as a limited company in Fredrikstad, Østfold with organisation number 923306129. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 31,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og utvikling av egen fast eiendom, samt alt som faller naturlig sammen med dette herunder investering i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 891,000 in revenue and NOK 585,000 in operating profit.

Key figures · 2025

Revenue
NOK 891,000
Operating profit
NOK 585,000
Equity
NOK −579,000
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
119.33
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.2%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DRONNINGENSGATE 39 AS?

BORG BYGGSYSTEMER AS
DRONNINGENSGATE 39 AS
NOK 891,000 rev. · NOK 585,000 profit

DRONNINGENSGATE 39 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRONNINGENSGATE 39 AS

Who owns DRONNINGENSGATE 39 AS?

BORG BYGGSYSTEMER AS is the largest registered owner, with 50.0%.

What is the revenue of DRONNINGENSGATE 39 AS?

DRONNINGENSGATE 39 AS had revenue of NOK 891,000 in 2025.

Where is DRONNINGENSGATE 39 AS based?

DRONNINGENSGATE 39 AS has its business address in Gamle Fredrikstad.

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.