BIZTRAC BETA
Freight transport by road

FRISVOLL VEIDRIFT AS

Org. no. 924921471 Limited company (AS) Molde Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 317,000
Equity NOK 2.8m
Incorporated 2020
Employees 5
Share capital NOK 100,000

FRISVOLL VEIDRIFT AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 924921471. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2020 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Godstransport på veg. Vintervedlikehold, feiing, brøytestikkersetting, kantklipping og alt i forbindelse med vegvedlikehold sommer og vinter.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 317,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 317,000
Equity
NOK 2.8m
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
5.28
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
42.0%
Very good
Equity as a share of total capital

Who owns FRISVOLL VEIDRIFT AS?

KJARTAN FINN FRISVOLL
FRISVOLL VEIDRIFT AS
NOK 5.5m rev. · NOK 317,000 profit

FRISVOLL VEIDRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRISVOLL VEIDRIFT AS

Who owns FRISVOLL VEIDRIFT AS?

KJARTAN FINN FRISVOLL is the largest registered owner, with 50.0%.

What is the revenue of FRISVOLL VEIDRIFT AS?

FRISVOLL VEIDRIFT AS had revenue of NOK 5.5m in 2025.

Who is the general manager of FRISVOLL VEIDRIFT AS?

Kjartan Finn Frisvoll is registered as general manager of FRISVOLL VEIDRIFT AS.

Where is FRISVOLL VEIDRIFT AS based?

FRISVOLL VEIDRIFT AS has its business address in Eresfjord.

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.