BIZTRAC BETA
Rental and operating of own or leased real estate

STOREBOTN 49 AS

Org. no. 929986199 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 2.3m
Equity NOK −1.1m
Incorporated 2022
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).

STOREBOTN 49 AS is registered as a limited company in Bergen, Vestland with organisation number 929986199. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utleie av egen eller leid fast eiendom ellers.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 2.3m
Equity
NOK −1.1m
Est. value
NOK 13.8m

Financial health · 2024

Liquidity
0.33
Not satisfactory
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 STOREBOTN 49 AS?

STORBERGEN EIENDOM AS
STOREBOTN 49 AS
NOK 3.8m rev. · NOK 2.3m profit

STOREBOTN 49 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STOREBOTN 49 AS

Who owns STOREBOTN 49 AS?

STORBERGEN EIENDOM AS is the largest registered owner, with 90.0%.

What is the revenue of STOREBOTN 49 AS?

STOREBOTN 49 AS had revenue of NOK 3.8m in 2024.

Who is the general manager of STOREBOTN 49 AS?

John-Rene Curran Sæthre is registered as general manager of STOREBOTN 49 AS.

Where is STOREBOTN 49 AS based?

STOREBOTN 49 AS has its business address in Eidsvåg I Åsane.

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.