BIZTRAC BETA
Support services to forestry

BÅTBERGET TRANSPORT AS

Org. no. 994219936 Limited company (AS) Sør-Fron Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 291,000
Equity NOK 810,000
Incorporated 2009
Share capital NOK 300,000

BÅTBERGET TRANSPORT AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 994219936. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2009. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Tømmertransport med bil på vei.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 291,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 291,000
Equity
NOK 810,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns BÅTBERGET TRANSPORT AS?

ARILD MAGNE BÅTBERGET
BÅTBERGET TRANSPORT AS
NOK 3.0m rev. · NOK 291,000 profit

BÅTBERGET TRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BÅTBERGET TRANSPORT AS own?

BÅTBERGET TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BÅTBERGET TRANSPORT AS

Who owns BÅTBERGET TRANSPORT AS?

ARILD MAGNE BÅTBERGET is the largest registered owner, with 50.0%.

What is the revenue of BÅTBERGET TRANSPORT AS?

BÅTBERGET TRANSPORT AS had revenue of NOK 3.0m in 2025.

Who is the general manager of BÅTBERGET TRANSPORT AS?

Arild Magne Båtberget is registered as general manager of BÅTBERGET TRANSPORT AS.

Where is BÅTBERGET TRANSPORT AS based?

BÅTBERGET TRANSPORT AS has its business address in Sør-Fron.

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.