BIZTRAC BETA
Other services incidental to land transport n.e.c.

BILBERGING INNLANDET AS

Org. no. 921183763 Limited company (AS) Gjøvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 35.4m
Operating profit NOK 1.1m
Equity NOK 5.9m
Incorporated 2018
Employees 22
Share capital NOK 500,000

BILBERGING INNLANDET AS is registered as a limited company in Gjøvik, Innlandet with organisation number 921183763. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2018 and has 22 registered employees. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Bilberging med dertil hørende tjenester, kjøp og salg, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 35.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 35.4m
Operating profit
NOK 1.1m
Equity
NOK 5.9m
Est. value
NOK 7.1m

Financial health · 2025

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

Who owns BILBERGING INNLANDET AS?

KJELL HARALD FOSS
BILBERGING INNLANDET AS
NOK 35.4m rev. · NOK 1.1m profit

BILBERGING INNLANDET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILBERGING INNLANDET AS

Who owns BILBERGING INNLANDET AS?

KJELL HARALD FOSS is the largest registered owner, with 50.0%.

What is the revenue of BILBERGING INNLANDET AS?

BILBERGING INNLANDET AS had revenue of NOK 35.4m in 2025.

Who is the general manager of BILBERGING INNLANDET AS?

Kjell Harald Foss is registered as general manager of BILBERGING INNLANDET AS.

Where is BILBERGING INNLANDET AS based?

BILBERGING INNLANDET AS has its business address in Hunndalen.

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.