BIZTRAC BETA
Restaurant activities

JARMANN 2 AS

Org. no. 921630727 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 22.2m
Operating profit NOK −89,000
Equity NOK 734,000
Incorporated 2018
Employees 19
Share capital NOK 100,000

Signals

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

JARMANN 2 AS is registered as a limited company in Oslo, Oslo with organisation number 921630727. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 19 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Restaurant, nattklubb og cateringvirksomhet, konsulenttjenester til andre restaurantører samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.2m in revenue and NOK −89,000 in operating profit.

Key figures · 2025

Revenue
NOK 22.2m
Operating profit
NOK −89,000
Equity
NOK 734,000
Est. value
NOK 15.9m

Financial health · 2025

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

Who owns JARMANN 2 AS?

AKERSHUSGRUPPEN BIDCO AS
JARMANN 2 AS
NOK 22.2m rev. · NOK −89,000 profit

JARMANN 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JARMANN 2 AS

Who owns JARMANN 2 AS?

AKERSHUSGRUPPEN BIDCO AS is the largest registered owner, with 100.0%.

What is the revenue of JARMANN 2 AS?

JARMANN 2 AS had revenue of NOK 22.2m in 2025.

Where is JARMANN 2 AS based?

JARMANN 2 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.