BIZTRAC BETA
Restaurant activities

22B MESTRING AS

Org. no. 924673273 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 704,000
Operating profit NOK −21,000
Equity NOK −725,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−725k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

22B MESTRING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924673273. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Hjelp til selvhjelp for utsatte.”. The most recent filed accounts, for the 2024 financial year, show NOK 704,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 704,000
Operating profit
NOK −21,000
Equity
NOK −725,000

Financial health · 2024

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

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

Who owns 22B MESTRING AS?

NORKIRKEN TRONDHEIM
22B MESTRING AS
NOK 704,000 rev. · NOK −21,000 profit

22B MESTRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 22B MESTRING AS

Who owns 22B MESTRING AS?

NORKIRKEN TRONDHEIM is the largest registered owner, with 100.0%.

What is the revenue of 22B MESTRING AS?

22B MESTRING AS had revenue of NOK 704,000 in 2024.

Who is the general manager of 22B MESTRING AS?

Daniel Muli Kawinzi is registered as general manager of 22B MESTRING AS.

Where is 22B MESTRING AS based?

22B MESTRING AS has its business address in Trondheim.

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.