BIZTRAC BETA
Uoppgitt

KVELI INVEST AS

Org. no. 930501166 Limited company (AS) Namsos Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK −10,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−10k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

KVELI INVEST AS is registered as a limited company in Namsos, Trøndelag with organisation number 930501166. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenesteytende virksomheter innen arrangement og konsulentarbeid innen dette. Videre salg av ulike tjenester samt investere i fast eiendom, kjøp, salg og utleie av disse. Ervervelse av løsøre og verdipapirer, samt ved aksjer eller på annen måte delta i annen virksomheter.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK −10,000

Financial health · 2025

Liquidity
0.62
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-61.0%
Weak
Equity as a share of total capital

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

Who owns KVELI INVEST AS?

JAN FRODE KVELI
KVELI INVEST AS
· NOK −7,000 profit

KVELI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KVELI INVEST AS own?

KVELI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KVELI INVEST AS

Who owns KVELI INVEST AS?

JAN FRODE KVELI is the largest registered owner, with 100.0%.

Who is the general manager of KVELI INVEST AS?

Jan Frode Kveli is registered as general manager of KVELI INVEST AS.

Where is KVELI INVEST AS based?

KVELI INVEST AS has its business address in Namsos.

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.