BIZTRAC BETA
Site preparation

WOLFRAM TRANSPORT AS

Org. no. 823417152 Limited company (AS) Modum Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 13.2m
Operating profit NOK −251,000
Equity NOK 659,000
Incorporated 2019
Employees 8
Share capital NOK 80,000

Signals

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

WOLFRAM TRANSPORT AS is registered as a limited company in Modum, Buskerud with organisation number 823417152. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 80,000, divided into 30 shares. The company's stated purpose is: “-Transport -Graving og bortkjøring av masser -Kosmetisk vedlikehold av kjøretøy”. The most recent filed accounts, for the 2024 financial year, show NOK 13.2m in revenue and NOK −251,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.2m
Operating profit
NOK −251,000
Equity
NOK 659,000
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns WOLFRAM TRANSPORT AS?

OLE KRISTIAN WOLFRAM
WOLFRAM TRANSPORT AS
NOK 13.2m rev. · NOK −251,000 profit

WOLFRAM TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WOLFRAM TRANSPORT AS

Who owns WOLFRAM TRANSPORT AS?

OLE KRISTIAN WOLFRAM is the largest registered owner, with 100.0%.

What is the revenue of WOLFRAM TRANSPORT AS?

WOLFRAM TRANSPORT AS had revenue of NOK 13.2m in 2024.

Who is the general manager of WOLFRAM TRANSPORT AS?

Ole Kristian Wolfram is registered as general manager of WOLFRAM TRANSPORT AS.

Where is WOLFRAM TRANSPORT AS based?

WOLFRAM TRANSPORT AS has its business address in Åmot.

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.