BIZTRAC BETA
Rental and operating of own or leased real estate

KLOSTERGT.12 AS

Org. no. 915838235 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 675,000
Operating profit NOK 121,000
Equity NOK 30,000
Incorporated 2015
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.

KLOSTERGT.12 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915838235. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 675,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2024

Revenue
NOK 675,000
Operating profit
NOK 121,000
Equity
NOK 30,000
Est. value
NOK 254,000

Financial health · 2024

Liquidity
0.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.9%
Weak
Equity as a share of total capital

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

Who owns KLOSTERGT.12 AS?

KREBREAL EIENDOM AS
KLOSTERGT.12 AS
NOK 675,000 rev. · NOK 121,000 profit

KLOSTERGT.12 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLOSTERGT.12 AS

Who owns KLOSTERGT.12 AS?

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

What is the revenue of KLOSTERGT.12 AS?

KLOSTERGT.12 AS had revenue of NOK 675,000 in 2024.

Where is KLOSTERGT.12 AS based?

KLOSTERGT.12 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.