BIZTRAC BETA
Business and other management consultancy activities

KROG & CO AS

Org. no. 948691825 Limited company (AS) Oslo Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 250,000
Operating profit NOK −19,000
Equity NOK 141,000
Incorporated 1988
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

KROG & CO AS is registered as a limited company in Oslo, Oslo with organisation number 948691825. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1988. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive bedriftsrådgivning samt annen virksomhet som står i forbindelse med dette. Selskapet kan samarbeide med, opprette eller delta i virksomhet med samme eller lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 250,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 250,000
Operating profit
NOK −19,000
Equity
NOK 141,000
Est. value
NOK 331,000

Financial health · 2024

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

Who owns KROG & CO AS?

HELGE KROG
KROG & CO AS
NOK 250,000 rev. · NOK −19,000 profit

KROG & CO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROG & CO AS

Who owns KROG & CO AS?

HELGE KROG is the largest registered owner, with 100.0%.

What is the revenue of KROG & CO AS?

KROG & CO AS had revenue of NOK 250,000 in 2024.

Who is the general manager of KROG & CO AS?

Helge Krog is registered as general manager of KROG & CO AS.

Where is KROG & CO AS based?

KROG & CO AS has its business address in Oslo.

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.