BIZTRAC BETA
Removal services

OSLO BYRÅET AS

Org. no. 927879131 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2023 NOK 0
Operating profit NOK −11,000
Equity NOK −5,000
Incorporated 2021
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−5k kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−11k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-20 Under avvikling registrert 2026-06-20.

OSLO BYRÅET AS is registered as a limited company in Oslo, Oslo with organisation number 927879131. The business is classified under removal services (NACE 49.420). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Flyttetjenester, logistikk og salg av konkursbo, herunder varer og kjøretøy, samt annen virksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2023 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2023

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −5,000

Financial health · 2023

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-31.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OSLO BYRÅET AS?

BLISS BEAUTY AS
OSLO BYRÅET AS
NOK 0 rev. · NOK −11,000 profit

OSLO BYRÅET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO BYRÅET AS

Who owns OSLO BYRÅET AS?

BLISS BEAUTY AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO BYRÅET AS?

OSLO BYRÅET AS had revenue of NOK 0 in 2023.

Where is OSLO BYRÅET AS based?

OSLO BYRÅET 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.