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

BILBERGING JÆREN AS

Org. no. 926681729 Limited company (AS) Time Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 742,000
Equity NOK 3.9m
Incorporated 2021
Employees 5
Share capital NOK 30,000

BILBERGING JÆREN AS is registered as a limited company in Time, Rogaland with organisation number 926681729. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen bilberging og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 742,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 742,000
Equity
NOK 3.9m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns BILBERGING JÆREN AS?

EGON UNDHEIM
BILBERGING JÆREN AS
NOK 4.8m rev. · NOK 742,000 profit

BILBERGING JÆREN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILBERGING JÆREN AS

Who owns BILBERGING JÆREN AS?

EGON UNDHEIM is the largest registered owner, with 100.0%.

What is the revenue of BILBERGING JÆREN AS?

BILBERGING JÆREN AS had revenue of NOK 4.8m in 2025.

Who is the general manager of BILBERGING JÆREN AS?

Egon Undheim is registered as general manager of BILBERGING JÆREN AS.

Where is BILBERGING JÆREN AS based?

BILBERGING JÆREN AS has its business address in Undheim.

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.