BIZTRAC BETA
Computer consultancy and computer facilities management activities

KLØKTIG INVEST AS

Org. no. 922308330 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 3.2m
Incorporated 2019
Share capital NOK 40,000

Signals

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

KLØKTIG INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 922308330. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 4000 shares. The company's stated purpose is: “Direkte eller gjennom datterselskaper å investere i fast eiendom, aksjer, og andre verdipapirer, samt virksomhet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −17,000
Equity
NOK 3.2m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns KLØKTIG INVEST AS?

ROGER HOEM-MARTINSEN
KLØKTIG INVEST AS
· NOK −17,000 profit

KLØKTIG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KLØKTIG INVEST AS own?

KLØKTIG INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Group structure

KLØKTIG INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about KLØKTIG INVEST AS

Who owns KLØKTIG INVEST AS?

ROGER HOEM-MARTINSEN is the largest registered owner, with 100.0%.

Who is the general manager of KLØKTIG INVEST AS?

Roger Hoem-Martinsen is registered as general manager of KLØKTIG INVEST AS.

Where is KLØKTIG INVEST AS based?

KLØKTIG INVEST 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.