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

CHRISMESS AS

Org. no. 921803672 Limited company (AS) Gjøvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 50.2m
Operating profit NOK 353,000
Equity NOK 996,000
Incorporated 2018
Employees 13
Share capital NOK 400,000

CHRISMESS AS is registered as a limited company in Gjøvik, Innlandet with organisation number 921803672. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2018 and has 13 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Dagligvarehandel med franchiserettigheter til Coop konseptet.”. The most recent filed accounts, for the 2025 financial year, show NOK 50.2m in revenue and NOK 353,000 in operating profit.

Key figures · 2025

Revenue
NOK 50.2m
▲ +4 %
Operating profit
NOK 353,000
▲ +1211 %
Equity
NOK 996,000
▲ +40 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.26
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
20.6%
Good
Equity as a share of total capital

Who owns CHRISMESS AS?

CHRISMESS AS
NOK 50.2m rev. · NOK 353,000 profit

CHRISMESS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHRISMESS AS

Who owns CHRISMESS AS?

Christopher Nilsen Messell is the largest registered owner, with 100.0%.

What is the revenue of CHRISMESS AS?

CHRISMESS AS had revenue of NOK 50.2m in 2025.

Who is the general manager of CHRISMESS AS?

Christopher Nilsen Messell is registered as general manager of CHRISMESS AS.

Where is CHRISMESS AS based?

CHRISMESS AS has its business address in Gjøvik.

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.