BIZTRAC BETA
Restaurant activities

SUB TRONDHEIM AS

Org. no. 921326076 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK −696,000
Equity NOK −818,000
Incorporated 2018
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−818k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−696k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SUB TRONDHEIM AS is registered as a limited company in Arendal, Agder with organisation number 921326076. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Yte serveringstjenester og salg av mat med alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK −696,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK −696,000
Equity
NOK −818,000

Financial health · 2024

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

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

Who owns SUB TRONDHEIM AS?

SUB HOLDING AS
SUB TRONDHEIM AS
NOK 4.3m rev. · NOK −696,000 profit

SUB TRONDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SUB TRONDHEIM AS

Who owns SUB TRONDHEIM AS?

SUB HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SUB TRONDHEIM AS?

SUB TRONDHEIM AS had revenue of NOK 4.3m in 2024.

Where is SUB TRONDHEIM AS based?

SUB TRONDHEIM AS has its business address in Arendal.

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.