BIZTRAC BETA
Computer consultancy and computer facilities management activities

KROGSTAD GRAPHICS AS

Org. no. 976002652 Limited company (AS) Asker Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 272,000
Incorporated 1995
Share capital NOK 100,000

Signals

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

KROGSTAD GRAPHICS AS is registered as a limited company in Asker, Akershus with organisation number 976002652. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produktutvikling av grafiske systemer, samt dertil relatert virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 272,000
Est. value
NOK 493,000

Financial health · 2025

Liquidity
-4.11
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
96.2%
Very good
Equity as a share of total capital

Who owns KROGSTAD GRAPHICS AS?

KNUT KROGSTAD
KROGSTAD GRAPHICS AS
NOK 0 rev. · NOK −4,000 profit

KROGSTAD GRAPHICS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KROGSTAD GRAPHICS AS

Who owns KROGSTAD GRAPHICS AS?

KNUT KROGSTAD is the largest registered owner, with 83.0%.

What is the revenue of KROGSTAD GRAPHICS AS?

KROGSTAD GRAPHICS AS had revenue of NOK 0 in 2025.

Who is the general manager of KROGSTAD GRAPHICS AS?

Knut Krogstad is registered as general manager of KROGSTAD GRAPHICS AS.

Where is KROGSTAD GRAPHICS AS based?

KROGSTAD GRAPHICS AS has its business address in Hvalstad.

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.