BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

KRUUSE NORGE AS

Org. no. 981389115 Limited company (AS) Ås Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 122.2m
Operating profit NOK 5.2m
Equity NOK 18.8m
Incorporated 1999
Share capital NOK 1.0m

Signals

1 flags
  • Nylig endring 2026-03-24 Adresseendring registrert 2026-03-24.

KRUUSE NORGE AS is registered as a limited company in Ås, Akershus with organisation number 981389115. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 1999. Registered share capital is NOK 1.0m, divided into 10 shares. The company's stated purpose is: “Handel med artikler til dyr samt hva hermed står i forbindelse, samt investeringsvirksomhet av enhver art, herunder kjøp av fast eiendom og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 122.2m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 122.2m
Operating profit
NOK 5.2m
Equity
NOK 18.8m
Est. value
NOK 31.8m

Financial health · 2024

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

Who owns KRUUSE NORGE AS?

JØRGEN KRUUSE A/S
KRUUSE NORGE AS
NOK 122.2m rev. · NOK 5.2m profit

KRUUSE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRUUSE NORGE AS

Who owns KRUUSE NORGE AS?

JØRGEN KRUUSE A/S is the largest registered owner, with 100.0%.

What is the revenue of KRUUSE NORGE AS?

KRUUSE NORGE AS had revenue of NOK 122.2m in 2024.

Who is the general manager of KRUUSE NORGE AS?

Jesper Poulsen is registered as general manager of KRUUSE NORGE AS.

Where is KRUUSE NORGE AS based?

KRUUSE NORGE AS has its business address in Ås.

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.