biztrac. BETA
COMPANY REGISTER PROFILE
928459012 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KVINLOG HOLDING AS

Org. no. 928459012 Limited company (AS) Flekkefjord Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 465,000
Incorporated 2021
Share capital NOK 520,000

Signals

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

KVINLOG HOLDING AS is registered as a limited company in Flekkefjord, Agder with organisation number 928459012. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 520,000, divided into 520000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −14,000
▼ −10 %
Equity
NOK 465,000
▼ −3 %
Est. value
NOK 546,000

Financial health · 2025

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

Who owns KVINLOG HOLDING AS?

KVINLOG HOLDING AS
· NOK −14,000 profit

KVINLOG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVINLOG HOLDING AS own?

KVINLOG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KVINLOG HOLDING AS

Who owns KVINLOG HOLDING AS?

Inge Kvinlog is the largest registered owner, with 100.0%.

Who is the general manager of KVINLOG HOLDING AS?

Inge Kvinlog is registered as general manager of KVINLOG HOLDING AS.

Where is KVINLOG HOLDING AS based?

KVINLOG HOLDING AS has its business address in Flekkefjord.

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.