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

KARASJOK BILBERGING AS

Org. no. 998551463 Limited company (AS) Karasjok Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 175,000
Equity NOK 389,000
Incorporated 2012
Employees 6
Share capital NOK 100,000

KARASJOK BILBERGING AS is registered as a limited company in Karasjok, Finnmark with organisation number 998551463. The business is classified under other services incidental to land transport n.e.c. (NACE 52.219). The company was incorporated in 2012 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bilberging og tjenesteyting naturlig forbundet med dette, samt annen virksomhet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 175,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 175,000
Equity
NOK 389,000
Est. value
NOK 504,000

Financial health · 2025

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.0%
Satisfactory
Equity as a share of total capital

Who owns KARASJOK BILBERGING AS?

RUNE OLSEN
KARASJOK BILBERGING AS
NOK 4.4m rev. · NOK 175,000 profit

KARASJOK BILBERGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARASJOK BILBERGING AS

Who owns KARASJOK BILBERGING AS?

RUNE OLSEN is the largest registered owner, with 100.0%.

What is the revenue of KARASJOK BILBERGING AS?

KARASJOK BILBERGING AS had revenue of NOK 4.4m in 2025.

Who is the general manager of KARASJOK BILBERGING AS?

Rune Olsen is registered as general manager of KARASJOK BILBERGING AS.

Where is KARASJOK BILBERGING AS based?

KARASJOK BILBERGING AS has its business address in Karasjok.

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.