BIZTRAC BETA
Restaurant activities

JORDBÆRPIKENE LAMBERTSETER AS

Org. no. 995204282 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 12.1m
Operating profit NOK 633,000
Equity NOK 233,000
Incorporated 2010
Employees 22
Share capital NOK 200,000

JORDBÆRPIKENE LAMBERTSETER AS is registered as a limited company in Oslo, Oslo with organisation number 995204282. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2010 and has 22 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 12.1m in revenue and NOK 633,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.1m
Operating profit
NOK 633,000
Equity
NOK 233,000
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns JORDBÆRPIKENE LAMBERTSETER AS?

LISS-HEGE SOLBAKKEN
JORDBÆRPIKENE LAMBERTSETER AS
NOK 12.1m rev. · NOK 633,000 profit

JORDBÆRPIKENE LAMBERTSETER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JORDBÆRPIKENE LAMBERTSETER AS

Who owns JORDBÆRPIKENE LAMBERTSETER AS?

LISS-HEGE SOLBAKKEN is the largest registered owner, with 100.0%.

What is the revenue of JORDBÆRPIKENE LAMBERTSETER AS?

JORDBÆRPIKENE LAMBERTSETER AS had revenue of NOK 12.1m in 2024.

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

Liss-Hege Solbakken is registered as general manager of JORDBÆRPIKENE LAMBERTSETER AS.

Where is JORDBÆRPIKENE LAMBERTSETER AS based?

JORDBÆRPIKENE LAMBERTSETER AS has its business address in Oslo.

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.