BIZTRAC BETA
COMPANY REGISTER PROFILE
952203541 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Repair and maintenance of motor vehicles

MAKS AUTO SERVIS AS

Org. no. 952203541 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 7.3m
Operating profit NOK 116,000
Equity NOK 223,000
Incorporated 1989
Share capital NOK 100,000

MAKS AUTO SERVIS AS is registered as a limited company in Oslo, Oslo with organisation number 952203541. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Reparasjon og service av motorkjøretøyer, herunder kjøp og salg av motorkjøretøyer og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.3m in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.3m
▼ −2 %
Operating profit
NOK 116,000
▼ −33 %
Equity
NOK 223,000
▼ −26 %
Est. value
NOK 587,000

Financial health · 2025

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
11.2%
Good
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns MAKS AUTO SERVIS AS?

MAKS AUTO SERVIS AS
NOK 7.3m rev. · NOK 116,000 profit

MAKS AUTO SERVIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MAKS AUTO SERVIS AS

Who owns MAKS AUTO SERVIS AS?

ALEKSANDER MAKSIC is the largest registered owner, with 100.0%.

What is the revenue of MAKS AUTO SERVIS AS?

MAKS AUTO SERVIS AS had revenue of NOK 7.3m in 2025.

Who is the general manager of MAKS AUTO SERVIS AS?

Aleksander Maksic is registered as general manager of MAKS AUTO SERVIS AS.

Where is MAKS AUTO SERVIS AS based?

MAKS AUTO SERVIS 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 02.09.2026.

Report a problem

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