BIZTRAC BETA
Restaurant activities

JORDBÆRPIKENE KANEBOGEN AS

Org. no. 918744169 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 982,000
Equity NOK 400,000
Incorporated 2017
Employees 19
Share capital NOK 400,000

JORDBÆRPIKENE KANEBOGEN AS is registered as a limited company in Harstad, Troms with organisation number 918744169. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 19 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Cafe- og serveringsvirksomhet og dermed alt som står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 982,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 982,000
Equity
NOK 400,000
Est. value
NOK 3.9m

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.7%
Satisfactory
Equity as a share of total capital

Who owns JORDBÆRPIKENE KANEBOGEN AS?

NINA KRISTIN NILSEN
JORDBÆRPIKENE KANEBOGEN AS
NOK 10.5m rev. · NOK 982,000 profit

JORDBÆRPIKENE KANEBOGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDBÆRPIKENE KANEBOGEN AS

Who owns JORDBÆRPIKENE KANEBOGEN AS?

NINA KRISTIN NILSEN is the largest registered owner, with 100.0%.

What is the revenue of JORDBÆRPIKENE KANEBOGEN AS?

JORDBÆRPIKENE KANEBOGEN AS had revenue of NOK 10.5m in 2024.

Who is the general manager of JORDBÆRPIKENE KANEBOGEN AS?

Nina Kristin Nilsen is registered as general manager of JORDBÆRPIKENE KANEBOGEN AS.

Where is JORDBÆRPIKENE KANEBOGEN AS based?

JORDBÆRPIKENE KANEBOGEN AS has its business address in Harstad.

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.