biztrac. BETA
COMPANY REGISTER PROFILE
889038772 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

KNOTTEN HOLDING AS

Org. no. 889038772 Limited company (AS) Larvik Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 4.9m
Incorporated 2005
Share capital NOK 130,000

Signals

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

KNOTTEN HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 889038772. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2005. Registered share capital is NOK 130,000, divided into 5 shares. The company's stated purpose is: “Eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Former names: MGK HOLDING AS

Key figures · 2025

Operating profit
NOK −24,000
▲ +80 %
Equity
NOK 4.9m
▼ −19 %
Est. value
NOK 6.1m

Financial health · 2025

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

Who owns KNOTTEN HOLDING AS?

KNOTTEN HOLDING AS
· NOK −24,000 profit

KNOTTEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KNOTTEN HOLDING AS own?

KNOTTEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KNOTTEN HOLDING AS

Who owns KNOTTEN HOLDING AS?

Gjermund Knotten is the largest registered owner, with 100.0%.

Where is KNOTTEN HOLDING AS based?

KNOTTEN HOLDING AS has its business address in Svarstad.

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.