BIZTRAC BETA
Rental and operating of own or leased real estate

TORGGT 25 NÆRING AS

Org. no. 932578018 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 124,000
Operating profit NOK −180,000
Equity NOK 39,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−180k kr).

TORGGT 25 NÆRING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932578018. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer og alt som står i forbindelse med dette, herunder å eie aksjer og andeler i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 124,000 in revenue and NOK −180,000 in operating profit.

Key figures · 2024

Revenue
NOK 124,000
Operating profit
NOK −180,000
Equity
NOK 39,000
Est. value
NOK 213,000

Financial health · 2025

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

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

Who owns TORGGT 25 NÆRING AS?

TORGGT 25 HOLDING AS
TORGGT 25 NÆRING AS
NOK 124,000 rev. · NOK −180,000 profit

TORGGT 25 NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TORGGT 25 NÆRING AS

Who owns TORGGT 25 NÆRING AS?

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

What is the revenue of TORGGT 25 NÆRING AS?

TORGGT 25 NÆRING AS had revenue of NOK 124,000 in 2024.

Where is TORGGT 25 NÆRING AS based?

TORGGT 25 NÆRING AS has its business address in Lillestrøm.

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.