BIZTRAC BETA
Retail sale of motor vehicles

SKIEN BILSALG AS

Org. no. 921807635 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK −119,000
Equity NOK 142,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−119k kr).

SKIEN BILSALG AS is registered as a limited company in Skien, Telemark with organisation number 921807635. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Bilforretning, verksted- og servicevirksomhet og hva dermed forøvrig står i forbindelse, herunder deltakelse i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK −119,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK −119,000
Equity
NOK 142,000
Est. value
NOK 408,000

Financial health · 2024

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.8%
Weak
Equity as a share of total capital

Who owns SKIEN BILSALG AS?

SKIEN BILSKADE OG VERKSTED HOLDING AS
SKIEN BILSALG AS
NOK 2.5m rev. · NOK −119,000 profit

SKIEN BILSALG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIEN BILSALG AS

Who owns SKIEN BILSALG AS?

SKIEN BILSKADE OG VERKSTED HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SKIEN BILSALG AS?

SKIEN BILSALG AS had revenue of NOK 2.5m in 2024.

Who is the general manager of SKIEN BILSALG AS?

Aleksander Lund is registered as general manager of SKIEN BILSALG AS.

Where is SKIEN BILSALG AS based?

SKIEN BILSALG AS has its business address in Skien.

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.