BIZTRAC BETA
Rental and operating of own or leased real estate

STOREBOTN 38 AS

Org. no. 918925600 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 929,000
Operating profit NOK 160,000
Equity NOK 10.2m
Incorporated 2017
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.

STOREBOTN 38 AS is registered as a limited company in Bergen, Vestland with organisation number 918925600. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av faste eiendom og alt som står naturlig i forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 929,000 in revenue and NOK 160,000 in operating profit.

Key figures · 2025

Revenue
NOK 929,000
Operating profit
NOK 160,000
Equity
NOK 10.2m
Est. value
NOK 7.4m

Financial health · 2025

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

Who owns STOREBOTN 38 AS?

ARETO INVEST AS
STOREBOTN 38 AS
NOK 929,000 rev. · NOK 160,000 profit

STOREBOTN 38 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOREBOTN 38 AS

Who owns STOREBOTN 38 AS?

ARETO INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of STOREBOTN 38 AS?

STOREBOTN 38 AS had revenue of NOK 929,000 in 2025.

Where is STOREBOTN 38 AS based?

STOREBOTN 38 AS has its business address in Laksevåg.

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.