BIZTRAC BETA
Computer programming activities

KRÜGER AS

Org. no. 993260053 Limited company (AS) Saltdal Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 2.3m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

KRÜGER AS is registered as a limited company in Saltdal, Nordland with organisation number 993260053. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av tjenester innenfor data og elektroteknikk og salg av produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp, salg og utvikling av eiendommer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 2.3m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns KRÜGER AS?

KJELL EMIL KRÜGER
KRÜGER AS
NOK 0 rev. · NOK −7,000 profit

KRÜGER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRÜGER AS own?

KRÜGER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KRÜGER AS

Who owns KRÜGER AS?

KJELL EMIL KRÜGER is the largest registered owner, with 100.0%.

What is the revenue of KRÜGER AS?

KRÜGER AS had revenue of NOK 0 in 2025.

Where is KRÜGER AS based?

KRÜGER AS has its business address in Rognan.

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.