BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

CHRIS HAMMERKVIST AS

Org. no. 992563842 Limited company (AS) Larvik Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −52,000
Equity NOK 11.3m
Incorporated 2008
Share capital NOK 30,000

Signals

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

CHRIS HAMMERKVIST AS is registered as a limited company in Larvik, Vestfold with organisation number 992563842. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2008. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å kjøpe, selge og leie ut eiendommer og annen virksomhet beslektet med denne.”.

Key figures · 2024

Operating profit
NOK −52,000
Equity
NOK 11.3m
Est. value
NOK 12.2m

Financial health · 2024

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

Who owns CHRIS HAMMERKVIST AS?

CHRIS ANDRE HAMMERKVIST
CHRIS HAMMERKVIST AS
· NOK −52,000 profit

CHRIS HAMMERKVIST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CHRIS HAMMERKVIST AS own?

CHRIS HAMMERKVIST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about CHRIS HAMMERKVIST AS

Who owns CHRIS HAMMERKVIST AS?

CHRIS ANDRE HAMMERKVIST is the largest registered owner, with 100.0%.

Who is the general manager of CHRIS HAMMERKVIST AS?

Chris Andre Hammerkvist is registered as general manager of CHRIS HAMMERKVIST AS.

Where is CHRIS HAMMERKVIST AS based?

CHRIS HAMMERKVIST AS has its business address in Larvik.

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.