biztrac. BETA
COMPANY REGISTER PROFILE
934232208 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

KNIGG INVEST AS

Org. no. 934232208 Limited company (AS) Grimstad Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −15,000
Equity NOK 89,000
Incorporated 2024
Share capital NOK 50,000

Signals

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

KNIGG INVEST AS is registered as a limited company in Grimstad, Agder with organisation number 934232208. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Drive med investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −15,000
▼ −9417 %
Equity
NOK 89,000
▲ +71 %
Est. value
NOK 182,000

Financial health · 2025

Liquidity
15.89
Very good
Current assets ÷ current liabilities
Profitability
26.1%
Very good
Return on total assets
Solidity
45.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KNIGG INVEST AS?

KNIGG INVEST AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about KNIGG INVEST AS

Who owns KNIGG INVEST AS?

Aleksander Storenes is the largest registered owner, with 20.0%.

What is the revenue of KNIGG INVEST AS?

KNIGG INVEST AS had revenue of NOK 0 in 2025.

Where is KNIGG INVEST AS based?

KNIGG INVEST AS has its business address in Grimstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.