BIZTRAC BETA
Restaurant activities

NO STRESS OSLO AS

Org. no. 919425296 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 9.3m
Operating profit NOK 330,000
Equity NOK 32,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NO STRESS OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 919425296. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive næringsvirksomhet, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.3m in revenue and NOK 330,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.3m
Operating profit
NOK 330,000
Equity
NOK 32,000
Est. value
NOK 1.2m

Financial health · 2024

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

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

Who owns NO STRESS OSLO AS?

BARGRUPPEN AS
NO STRESS OSLO AS
NOK 9.3m rev. · NOK 330,000 profit

NO STRESS OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NO STRESS OSLO AS

Who owns NO STRESS OSLO AS?

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

What is the revenue of NO STRESS OSLO AS?

NO STRESS OSLO AS had revenue of NOK 9.3m in 2024.

Who is the general manager of NO STRESS OSLO AS?

Jan Thomas Monclair is registered as general manager of NO STRESS OSLO AS.

Where is NO STRESS OSLO AS based?

NO STRESS OSLO 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.