biztrac. BETA
COMPANY REGISTER PROFILE
928822362 ORG. NO. 2022 ACCOUNTS 8 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠TOJO MAT AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Restaurant activities

TOJO MAT AS

Org. no. 928822362 Limited company (AS) Bardu Incorporated 2022 Compulsory dissolution
Revenue 2022 NOK 1.2m
Operating profit NOK −248,000
Equity NOK −227,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

TOJO MAT AS is registered as a limited company in Bardu, Troms with organisation number 928822362. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift.”. The most recent filed accounts, for the 2022 financial year, show NOK 1.2m in revenue and NOK −248,000 in operating profit.

Key figures · 2022

Revenue
NOK 1.2m
Operating profit
NOK −248,000
Equity
NOK −227,000

Financial health · 2022

Liquidity
0.53
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-38.5%
Weak
Equity as a share of total capital

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

Who owns TOJO MAT AS?

TOJO MAT AS
NOK 1.2m rev. · NOK −248,000 profit

TOJO MAT AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2022.

All shareholders and roles →

Frequently asked questions about TOJO MAT AS

Who owns TOJO MAT AS?

Tom André Johnsen is the largest registered owner, with 100.0%.

What is the revenue of TOJO MAT AS?

TOJO MAT AS had revenue of NOK 1.2m in 2022.

Where is TOJO MAT AS based?

TOJO MAT AS has its business address in Bardu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.