BIZTRAC BETA
Rental and operating of own or leased real estate

STORGATA 1 NÆRING AS

Org. no. 934653289 Limited company (AS) Moss Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 525,000
Operating profit NOK 17,000
Equity NOK 1.2m
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 1 NÆRING AS is registered as a limited company in Moss, Østfold with organisation number 934653289. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive eiendomsvirksomhet, herunder kjøp, salg, forvaltning og utleie av fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 525,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 525,000
Operating profit
NOK 17,000
Equity
NOK 1.2m
Est. value
NOK 853,000

Financial health · 2025

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

Who owns STORGATA 1 NÆRING AS?

HERDE EIENDOM AS
STORGATA 1 NÆRING AS
NOK 525,000 rev. · NOK 17,000 profit

STORGATA 1 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STORGATA 1 NÆRING AS

Who owns STORGATA 1 NÆRING AS?

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

What is the revenue of STORGATA 1 NÆRING AS?

STORGATA 1 NÆRING AS had revenue of NOK 525,000 in 2025.

Where is STORGATA 1 NÆRING AS based?

STORGATA 1 NÆRING AS has its business address in Rygge.

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.