biztrac. BETA
COMPANY REGISTER PROFILE
993456284 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

FIX BIL OLSVIK AS

Org. no. 993456284 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 8.6m
Operating profit NOK 167,000
Equity NOK 163,000
Incorporated 2008
Employees 7
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.

FIX BIL OLSVIK AS is registered as a limited company in Bergen, Vestland with organisation number 993456284. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av bilverksted og alt som har tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.6m in revenue and NOK 167,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.6m
▼ −1 %
Operating profit
NOK 167,000
▼ −55 %
Equity
NOK 163,000
▲ +1 %
Est. value
NOK 798,000

Financial health · 2025

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
11.9%
Good
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns FIX BIL OLSVIK AS?

FIX BIL OLSVIK AS
NOK 8.6m rev. · NOK 167,000 profit

FIX BIL OLSVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIX BIL OLSVIK AS

Who owns FIX BIL OLSVIK AS?

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

What is the revenue of FIX BIL OLSVIK AS?

FIX BIL OLSVIK AS had revenue of NOK 8.6m in 2025.

Where is FIX BIL OLSVIK AS based?

FIX BIL OLSVIK AS has its business address in Olsvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.