BIZTRAC BETA
Development of building projects

TORGGATA 22 AS

Org. no. 932912066 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 344,000
Operating profit NOK 295,000
Equity NOK 1.2m
Incorporated 2023
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.

TORGGATA 22 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932912066. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 120 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, herunder drive utvikling av eiendom samt virksomhet beslektet med dette, og deltagelse i andre selskaper med virksomhet som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 344,000 in revenue and NOK 295,000 in operating profit.

Key figures · 2024

Revenue
NOK 344,000
Operating profit
NOK 295,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
1.36
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
80.3%
Very good
Equity as a share of total capital

Who owns TORGGATA 22 AS?

MICAELSEN EIENDOM HOLDING AS
TORGGATA 22 AS
NOK 344,000 rev. · NOK 295,000 profit

TORGGATA 22 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORGGATA 22 AS

Who owns TORGGATA 22 AS?

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

What is the revenue of TORGGATA 22 AS?

TORGGATA 22 AS had revenue of NOK 344,000 in 2024.

Where is TORGGATA 22 AS based?

TORGGATA 22 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.