BIZTRAC BETA
Other technical consultancy

KAT CONSULTING DC AS

Org. no. 934551834 Limited company (AS) Lørenskog Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 110,000
Operating profit NOK 13,000
Equity NOK 255,000
Incorporated 2024
Share capital NOK 250,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KAT CONSULTING DC AS is registered as a limited company in Lørenskog, Akershus with organisation number 934551834. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2024. Registered share capital is NOK 250,000, divided into 1000 shares. The company's stated purpose is: “Teknisk konsulenttjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 110,000 in revenue and NOK 13,000 in operating profit.

Key figures · 2024

Revenue
NOK 110,000
Operating profit
NOK 13,000
Equity
NOK 255,000
Est. value
NOK 218,000

Financial health · 2024

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

Who owns KAT CONSULTING DC AS?

KAT GROUP AS
KAT CONSULTING DC AS
NOK 110,000 rev. · NOK 13,000 profit

KAT CONSULTING DC AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAT CONSULTING DC AS

Who owns KAT CONSULTING DC AS?

KAT GROUP AS is the largest registered owner, with 80.0%.

What is the revenue of KAT CONSULTING DC AS?

KAT CONSULTING DC AS had revenue of NOK 110,000 in 2024.

Who is the general manager of KAT CONSULTING DC AS?

Andreas Storsveen Romøren is registered as general manager of KAT CONSULTING DC AS.

Where is KAT CONSULTING DC AS based?

KAT CONSULTING DC AS has its business address in Fjellhamar.

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.