BIZTRAC BETA
Rental and operating of own or leased real estate

STOREBOTN 12 AS

Org. no. 919916532 Limited company (AS) Askøy Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 710,000
Equity NOK 829,000
Incorporated 2017
Share capital NOK 500,000

Signals

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

STOREBOTN 12 AS is registered as a limited company in Askøy, Vestland with organisation number 919916532. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 500,000, divided into 100 shares. The company's stated purpose is: “Drift og utleie av fast eiendom, og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 710,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 710,000
Equity
NOK 829,000
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.2%
Weak
Equity as a share of total capital

Who owns STOREBOTN 12 AS?

SEMA HOLDING AS
STOREBOTN 12 AS
NOK 1.2m rev. · NOK 710,000 profit

STOREBOTN 12 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREBOTN 12 AS

Who owns STOREBOTN 12 AS?

SEMA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STOREBOTN 12 AS?

STOREBOTN 12 AS had revenue of NOK 1.2m in 2024.

Who is the general manager of STOREBOTN 12 AS?

Marit Gulbrandsøy Haugland is registered as general manager of STOREBOTN 12 AS.

Where is STOREBOTN 12 AS based?

STOREBOTN 12 AS has its business address in Kleppestø.

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.