BIZTRAC BETA
Development of building projects

STORGATA 32 FREDRIKSTAD AS

Org. no. 934981642 Limited company (AS) Fredrikstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 2.9m
Equity NOK 9.5m
Incorporated 2024
Share capital NOK 100,000

Signals

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

STORGATA 32 FREDRIKSTAD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 934981642. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, utvikling, drift og salg av eiendom, samt virksomhet som naturlig står i sammenheng med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 2.9m
Equity
NOK 9.5m
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns STORGATA 32 FREDRIKSTAD AS?

FREDRIKSBORG EIENDOM AS
STORGATA 32 FREDRIKSTAD AS
NOK 6.7m rev. · NOK 2.9m profit

STORGATA 32 FREDRIKSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORGATA 32 FREDRIKSTAD AS

Who owns STORGATA 32 FREDRIKSTAD AS?

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

What is the revenue of STORGATA 32 FREDRIKSTAD AS?

STORGATA 32 FREDRIKSTAD AS had revenue of NOK 6.7m in 2025.

Where is STORGATA 32 FREDRIKSTAD AS based?

STORGATA 32 FREDRIKSTAD AS has its business address in 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.