BIZTRAC BETA
Repair and maintenance of motor vehicles

NESBYEN AUTO AS

Org. no. 982978777 Limited company (AS) Nesbyen Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 227.1m
Operating profit NOK 9.4m
Equity NOK 6.5m
Incorporated 2001
Employees 24
Share capital NOK 2.0m

Signals

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

NESBYEN AUTO AS is registered as a limited company in Nesbyen, Buskerud with organisation number 982978777. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2001 and has 24 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Kjøp og salg av biler, verkstedsdrift og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 227.1m in revenue and NOK 9.4m in operating profit.

Key figures · 2025

Revenue
NOK 227.1m
Operating profit
NOK 9.4m
Equity
NOK 6.5m
Est. value
NOK 38.8m

Financial health · 2025

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.0%
Good
Equity as a share of total capital

Who owns NESBYEN AUTO AS?

XPND AS
NESBYEN AUTO AS
NOK 227.1m rev. · NOK 9.4m profit

NESBYEN AUTO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESBYEN AUTO AS

Who owns NESBYEN AUTO AS?

XPND AS is the largest registered owner, with 100.0%.

What is the revenue of NESBYEN AUTO AS?

NESBYEN AUTO AS had revenue of NOK 227.1m in 2025.

Who is the general manager of NESBYEN AUTO AS?

Anders Olav Frydenlund is registered as general manager of NESBYEN AUTO AS.

Where is NESBYEN AUTO AS based?

NESBYEN AUTO AS has its business address in Nesbyen.

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.