BIZTRAC BETA
Restaurant activities

JORDBÆRPIKENE GULSKOGEN AS

Org. no. 997077237 Limited company (AS) Drammen Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK 228,000
Equity NOK 201,000
Incorporated 2011
Employees 14
Share capital NOK 200,000

JORDBÆRPIKENE GULSKOGEN AS is registered as a limited company in Drammen, Buskerud with organisation number 997077237. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2011 and has 14 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Cafe- og serveringsvirksomhet, og dermed alt som står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK 228,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK 228,000
Equity
NOK 201,000
Est. value
NOK 952,000

Financial health · 2024

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

Who owns JORDBÆRPIKENE GULSKOGEN AS?

ANETTE GULBRANDSEN
JORDBÆRPIKENE GULSKOGEN AS
NOK 11.0m rev. · NOK 228,000 profit

JORDBÆRPIKENE GULSKOGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDBÆRPIKENE GULSKOGEN AS

Who owns JORDBÆRPIKENE GULSKOGEN AS?

ANETTE GULBRANDSEN is the largest registered owner, with 100.0%.

What is the revenue of JORDBÆRPIKENE GULSKOGEN AS?

JORDBÆRPIKENE GULSKOGEN AS had revenue of NOK 11.0m in 2024.

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

Mohammad Hashir Awan is registered as general manager of JORDBÆRPIKENE GULSKOGEN AS.

Where is JORDBÆRPIKENE GULSKOGEN AS based?

JORDBÆRPIKENE GULSKOGEN AS has its business address in Drammen.

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.