BIZTRAC BETA
Rental and operating of own or leased real estate

GYLDENLØVES GATE 15A AS

Org. no. 925481831 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 617,000
Equity NOK 3.5m
Incorporated 2020
Share capital NOK 54,000

Signals

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

GYLDENLØVES GATE 15A AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925481831. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 54,000, divided into 53535 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 2025 financial year, show NOK 1.1m in revenue and NOK 617,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 617,000
Equity
NOK 3.5m
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.8%
Good
Equity as a share of total capital

Who owns GYLDENLØVES GATE 15A AS?

BREVIK BOLIGUTLEIE AS
GYLDENLØVES GATE 15A AS
NOK 1.1m rev. · NOK 617,000 profit

GYLDENLØVES GATE 15A AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYLDENLØVES GATE 15A AS

Who owns GYLDENLØVES GATE 15A AS?

BREVIK BOLIGUTLEIE AS is the largest registered owner, with 100.0%.

What is the revenue of GYLDENLØVES GATE 15A AS?

GYLDENLØVES GATE 15A AS had revenue of NOK 1.1m in 2025.

Where is GYLDENLØVES GATE 15A AS based?

GYLDENLØVES GATE 15A 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.