biztrac. BETA
COMPANY REGISTER PROFILE
922336768 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BN TROMSØ AS

Org. no. 922336768 Limited company (AS) Trondheim Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −68,000
Equity NOK 40,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−68k kr).

BN TROMSØ AS is registered as a limited company in Trondheim, Trøndelag with organisation number 922336768. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie fast eiendom eller aksjer i selskaper som eier fast eiendom, utvikle, omsette, leie ut og for øvrig administrere fast eiendom, samt hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −68,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −68,000
▼ −38 %
Equity
NOK 40,000
▼ −62 %
Est. value
NOK 37,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-90.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns BN TROMSØ AS?

BN TROMSØ AS
NOK 0 rev. · NOK −68,000 profit

BN TROMSØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BN TROMSØ AS

Who owns BN TROMSØ AS?

BOLIG NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of BN TROMSØ AS?

BN TROMSØ AS had revenue of NOK 0 in 2025.

Where is BN TROMSØ AS based?

BN TROMSØ 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.