BIZTRAC BETA
Rental and operating of own or leased real estate

TRIBUNEBYGG AS

Org. no. 915113907 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK 4.2m
Equity NOK 9.0m
Incorporated 2015
Share capital NOK 241,000

Signals

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

TRIBUNEBYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 915113907. 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 241,000, divided into 800 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 6.8m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK 4.2m
Equity
NOK 9.0m
Est. value
NOK 9.3m

Financial health · 2024

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns TRIBUNEBYGG AS?

ZOLEN & MÅNEN AS
TRIBUNEBYGG AS
NOK 6.8m rev. · NOK 4.2m profit

TRIBUNEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRIBUNEBYGG AS

Who owns TRIBUNEBYGG AS?

ZOLEN & MÅNEN AS is the largest registered owner, with 100.0%.

What is the revenue of TRIBUNEBYGG AS?

TRIBUNEBYGG AS had revenue of NOK 6.8m in 2024.

Who is the general manager of TRIBUNEBYGG AS?

Robert Sotberg is registered as general manager of TRIBUNEBYGG AS.

Where is TRIBUNEBYGG AS based?

TRIBUNEBYGG 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.