BIZTRAC BETA
Wholesale of other intermediate products

KONGSBERG TRADING AS

Org. no. 921224648 Limited company (AS) Kongsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 17.9m
Operating profit NOK 1.3m
Equity NOK 2.5m
Incorporated 2018
Share capital NOK 30,000

KONGSBERG TRADING AS is registered as a limited company in Kongsberg, Buskerud with organisation number 921224648. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med kjøp og salg av produkter innenfor papir med tilhørende produkter og se på nye produkter som selskapet kan bistå med salg på. Selskapet vil drive handel i og utenfor Norge.”. The most recent filed accounts, for the 2025 financial year, show NOK 17.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 17.9m
Operating profit
NOK 1.3m
Equity
NOK 2.5m
Est. value
NOK 6.4m

Financial health · 2025

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

Who owns KONGSBERG TRADING AS?

FRANK SANDBERG
KONGSBERG TRADING AS
NOK 17.9m rev. · NOK 1.3m profit

KONGSBERG TRADING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGSBERG TRADING AS

Who owns KONGSBERG TRADING AS?

FRANK SANDBERG is the largest registered owner, with 100.0%.

What is the revenue of KONGSBERG TRADING AS?

KONGSBERG TRADING AS had revenue of NOK 17.9m in 2025.

Who is the general manager of KONGSBERG TRADING AS?

Frank Sandberg is registered as general manager of KONGSBERG TRADING AS.

Where is KONGSBERG TRADING AS based?

KONGSBERG TRADING AS has its business address in Kongsberg.

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.