BIZTRAC BETA
Repair and maintenance of motor vehicles

OSLO BILSERVICE AS

Org. no. 989582631 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 25,000
Equity NOK −75,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

OSLO BILSERVICE AS is registered as a limited company in Oslo, Oslo with organisation number 989582631. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av bilverksted, omsetning av bilrekvisita og ellers beslektet under slik virksomhet og bilsalg.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 25,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 25,000
Equity
NOK −75,000
Est. value
NOK 189,000

Financial health · 2024

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

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

Who owns OSLO BILSERVICE AS?

YENAL ØTGUN
OSLO BILSERVICE AS
NOK 3.4m rev. · NOK 25,000 profit

OSLO BILSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLO BILSERVICE AS

Who owns OSLO BILSERVICE AS?

YENAL ØTGUN is the largest registered owner, with 50.0%.

What is the revenue of OSLO BILSERVICE AS?

OSLO BILSERVICE AS had revenue of NOK 3.4m in 2024.

Who is the general manager of OSLO BILSERVICE AS?

Muammer Øtgun is registered as general manager of OSLO BILSERVICE AS.

Where is OSLO BILSERVICE AS based?

OSLO BILSERVICE 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.