BIZTRAC BETA
Restaurant activities

JORDBÆRPIKENE BRYNE AS

Org. no. 912257436 Limited company (AS) Time Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK −316,000
Equity NOK 0
Incorporated 2013
Employees 16
Share capital NOK 200,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−316k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JORDBÆRPIKENE BRYNE AS is registered as a limited company in Time, Rogaland with organisation number 912257436. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013 and has 16 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Cafè- og serveringsvirksomhet, og dermed alt som står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK −316,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK −316,000
Equity
NOK 0

Financial health · 2024

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

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

Who owns JORDBÆRPIKENE BRYNE AS?

JPN AS
JORDBÆRPIKENE BRYNE AS
NOK 7.9m rev. · NOK −316,000 profit

JORDBÆRPIKENE BRYNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDBÆRPIKENE BRYNE AS

Who owns JORDBÆRPIKENE BRYNE AS?

JPN AS is the largest registered owner, with 100.0%.

What is the revenue of JORDBÆRPIKENE BRYNE AS?

JORDBÆRPIKENE BRYNE AS had revenue of NOK 7.9m in 2024.

Where is JORDBÆRPIKENE BRYNE AS based?

JORDBÆRPIKENE BRYNE AS has its business address in Bryne.

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.