BIZTRAC BETA
Wholesale of other machinery and equipment

SERVICE-EKSPRESSEN AS

Org. no. 936328865 Limited company (AS) Bergen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 28.6m
Operating profit NOK 4.8m
Equity NOK 5.7m
Incorporated 2025
Employees 7
Share capital NOK 370,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-09-22.

SERVICE-EKSPRESSEN AS is registered as a limited company in Bergen, Vestland with organisation number 936328865. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2025 and has 7 registered employees. Registered share capital is NOK 370,000, divided into 50 shares. The company's stated purpose is: “Handel og service av bilverkstedutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.6m in revenue and NOK 4.8m in operating profit.

Key figures · 2025

Revenue
NOK 28.6m
Operating profit
NOK 4.8m
Equity
NOK 5.7m
Est. value
NOK 17.9m

Financial health · 2025

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

Who owns SERVICE-EKSPRESSEN AS?

SERVICE-EKSPRESSEN HOLDING AS
SERVICE-EKSPRESSEN AS
NOK 28.6m rev. · NOK 4.8m profit

SERVICE-EKSPRESSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SERVICE-EKSPRESSEN AS

Who owns SERVICE-EKSPRESSEN AS?

SERVICE-EKSPRESSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SERVICE-EKSPRESSEN AS?

SERVICE-EKSPRESSEN AS had revenue of NOK 28.6m in 2025.

Who is the general manager of SERVICE-EKSPRESSEN AS?

Christer Jensen is registered as general manager of SERVICE-EKSPRESSEN AS.

Where is SERVICE-EKSPRESSEN AS based?

SERVICE-EKSPRESSEN AS has its business address in Nesttun.

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.