BIZTRAC BETA
Rental and operating of own or leased real estate

NEDRE MØLLENBERG GT 59 II AS

Org. no. 822758932 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.4m
Equity NOK 2.7m
Incorporated 2019
Share capital NOK 30,000

NEDRE MØLLENBERG GT 59 II AS is registered as a limited company in Trondheim, Trøndelag with organisation number 822758932. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Utleie av fast eiendom og annet som naturlig faller herunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.4m
Equity
NOK 2.7m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns NEDRE MØLLENBERG GT 59 II AS?

BREVIK BOLIGUTLEIE AS
NEDRE MØLLENBERG GT 59 II AS
NOK 1.9m rev. · NOK 1.4m profit

NEDRE MØLLENBERG GT 59 II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEDRE MØLLENBERG GT 59 II AS

Who owns NEDRE MØLLENBERG GT 59 II AS?

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

What is the revenue of NEDRE MØLLENBERG GT 59 II AS?

NEDRE MØLLENBERG GT 59 II AS had revenue of NOK 1.9m in 2025.

Who is the general manager of NEDRE MØLLENBERG GT 59 II AS?

Ragnar Martin Brevik is registered as general manager of NEDRE MØLLENBERG GT 59 II AS.

Where is NEDRE MØLLENBERG GT 59 II AS based?

NEDRE MØLLENBERG GT 59 II 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.