biztrac. BETA
COMPANY REGISTER PROFILE
928723240 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

FINE TRANSPORT AS

Org. no. 928723240 Limited company (AS) Drammen Incorporated 2022 Active
Revenue 2025 NOK 8.2m
Operating profit NOK −214,000
Equity NOK 53,000
Incorporated 2022
Employees 10
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−214k kr).

FINE TRANSPORT AS is registered as a limited company in Drammen, Buskerud with organisation number 928723240. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2022 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Transport og frakt av gods og varer, i inn-og utland. Spedisjonsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK −214,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
▼ −27 %
Operating profit
NOK −214,000
▼ −163 %
Equity
NOK 53,000
▼ −90 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
0.94
Weak
Current assets ÷ current liabilities
Profitability
-11.2%
Not satisfactory
Return on total assets
Solidity
3.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FINE TRANSPORT AS?

FINE TRANSPORT AS
NOK 8.2m rev. · NOK −214,000 profit

FINE TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINE TRANSPORT AS

Who owns FINE TRANSPORT AS?

Karol Wiacek is the largest registered owner, with 100.0%.

What is the revenue of FINE TRANSPORT AS?

FINE TRANSPORT AS had revenue of NOK 8.2m in 2025.

Where is FINE TRANSPORT AS based?

FINE TRANSPORT AS has its business address in Krokstadelva.

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.