BIZTRAC BETA
Non-scheduled passenger transport by road

K.RINGBERG KRAN OG TRANSPORT AS

Org. no. 989410539 Limited company (AS) Tromsø Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK 941,000
Equity NOK 1.1m
Incorporated 2006
Share capital NOK 100,000

K.RINGBERG KRAN OG TRANSPORT AS is registered as a limited company in Tromsø, Troms with organisation number 989410539. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport av varer, lagerarbeid og vedlikehold.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK 941,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK 941,000
Equity
NOK 1.1m
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.6%
Good
Equity as a share of total capital

Who owns K.RINGBERG KRAN OG TRANSPORT AS?

KENNETH RINGBERG
K.RINGBERG KRAN OG TRANSPORT AS
NOK 6.2m rev. · NOK 941,000 profit

K.RINGBERG KRAN OG TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about K.RINGBERG KRAN OG TRANSPORT AS

Who owns K.RINGBERG KRAN OG TRANSPORT AS?

KENNETH RINGBERG is the largest registered owner, with 100.0%.

What is the revenue of K.RINGBERG KRAN OG TRANSPORT AS?

K.RINGBERG KRAN OG TRANSPORT AS had revenue of NOK 6.2m in 2024.

Who is the general manager of K.RINGBERG KRAN OG TRANSPORT AS?

Kenneth Ringberg is registered as general manager of K.RINGBERG KRAN OG TRANSPORT AS.

Where is K.RINGBERG KRAN OG TRANSPORT AS based?

K.RINGBERG KRAN OG TRANSPORT AS has its business address in Tromsø.

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.