BIZTRAC BETA
Rental and operating of own or leased real estate

THM 33 NÆRING AS

Org. no. 933474186 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 874,000
Equity NOK 31,000
Incorporated 2024
Share capital NOK 37,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-20 Adresseendring registrert 2026-02-20.

THM 33 NÆRING AS is registered as a limited company in Oslo, Oslo with organisation number 933474186. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 37,000, divided into 30000 shares. The company's stated purpose is: “Eie og drift av fast eiendom og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 874,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 874,000
Equity
NOK 31,000
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.1%
Weak
Equity as a share of total capital

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

Who owns THM 33 NÆRING AS?

MARKVEIEN 48 AS
THM 33 NÆRING AS
NOK 1.0m rev. · NOK 874,000 profit

THM 33 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about THM 33 NÆRING AS

Who owns THM 33 NÆRING AS?

MARKVEIEN 48 AS is the largest registered owner, with 100.0%.

What is the revenue of THM 33 NÆRING AS?

THM 33 NÆRING AS had revenue of NOK 1.0m in 2024.

Where is THM 33 NÆRING AS based?

THM 33 NÆRING 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.