BIZTRAC BETA
Rental and operating of own or leased real estate

TEATERGATA 1 AS

Org. no. 926674528 Limited company (AS) Lillestrøm Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 120,000
Operating profit NOK 79,000
Equity NOK 15.2m
Incorporated 2021
Share capital NOK 120,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TEATERGATA 1 AS is registered as a limited company in Lillestrøm, Akershus with organisation number 926674528. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 120,000, divided into 300 shares. The company's stated purpose is: “Investering i-, utvikling- og utleie av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 120,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2024

Revenue
NOK 120,000
Operating profit
NOK 79,000
Equity
NOK 15.2m
Est. value
NOK 10.6m

Financial health · 2024

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

Who owns TEATERGATA 1 AS?

PLANTAX HOLDING AS
TEATERGATA 1 AS
NOK 120,000 rev. · NOK 79,000 profit

TEATERGATA 1 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

TEATERGATA 1 AS er morselskap for 7 datterselskaper:

Frequently asked questions about TEATERGATA 1 AS

Who owns TEATERGATA 1 AS?

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

What is the revenue of TEATERGATA 1 AS?

TEATERGATA 1 AS had revenue of NOK 120,000 in 2024.

Where is TEATERGATA 1 AS based?

TEATERGATA 1 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.