BIZTRAC BETA
Development of building projects

TRE PÅ BERGAN AS

Org. no. 925655708 Limited company (AS) Dyrøy Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 1.3m

Signals

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

TRE PÅ BERGAN AS is registered as a limited company in Dyrøy, Troms with organisation number 925655708. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 1.3m, divided into 13000 shares. The company's stated purpose is: “Eie og /eller delta i andre selskap, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 1.2m
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns TRE PÅ BERGAN AS?

TOM ROBIN EDVARDSEN
TRE PÅ BERGAN AS
NOK 0 rev. · NOK −24,000 profit

TRE PÅ BERGAN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRE PÅ BERGAN AS own?

TRE PÅ BERGAN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about TRE PÅ BERGAN AS

Who owns TRE PÅ BERGAN AS?

TOM ROBIN EDVARDSEN is the largest registered owner, with 100.0%.

What is the revenue of TRE PÅ BERGAN AS?

TRE PÅ BERGAN AS had revenue of NOK 0 in 2025.

Where is TRE PÅ BERGAN AS based?

TRE PÅ BERGAN AS has its business address in Brøstadbotn.

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.