BIZTRAC BETA
Rental and operating of own or leased real estate

SØREN BULLS VEI 27 AS

Org. no. 923594183 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK 4.0m
Equity NOK 5.9m
Incorporated 2019
Share capital NOK 90,000

Signals

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

SØREN BULLS VEI 27 AS is registered as a limited company in Oslo, Oslo with organisation number 923594183. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 90,000, divided into 30 shares. The company's stated purpose is: “kjøp, drift og salg av eiendommer og andre driftsmidler, kjøp, eie og salg av aksjer og andre verdipapirer, deltagelse i andre forretningsforetagender, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK 4.0m in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK 4.0m
Equity
NOK 5.9m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns SØREN BULLS VEI 27 AS?

MARBY EIENDOM AS
SØREN BULLS VEI 27 AS
NOK 6.2m rev. · NOK 4.0m profit

SØREN BULLS VEI 27 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØREN BULLS VEI 27 AS

Who owns SØREN BULLS VEI 27 AS?

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

What is the revenue of SØREN BULLS VEI 27 AS?

SØREN BULLS VEI 27 AS had revenue of NOK 6.2m in 2024.

Where is SØREN BULLS VEI 27 AS based?

SØREN BULLS VEI 27 AS has its business address in Oslo.

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.