BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGPARTNER TRONDHEIM AS

Org. no. 913792572 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 156,000
Equity NOK 238,000
Incorporated 2014
Share capital NOK 30,000

BYGGPARTNER TRONDHEIM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 913792572. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppussing og renovering av bad og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 156,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 156,000
Equity
NOK 238,000
Est. value
NOK 645,000

Financial health · 2025

Liquidity
1.91
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
50.5%
Very good
Equity as a share of total capital

Who owns BYGGPARTNER TRONDHEIM AS?

TOMMY BULL
BYGGPARTNER TRONDHEIM AS
NOK 2.8m rev. · NOK 156,000 profit

BYGGPARTNER TRONDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGPARTNER TRONDHEIM AS

Who owns BYGGPARTNER TRONDHEIM AS?

TOMMY BULL is the largest registered owner, with 100.0%.

What is the revenue of BYGGPARTNER TRONDHEIM AS?

BYGGPARTNER TRONDHEIM AS had revenue of NOK 2.8m in 2025.

Who is the general manager of BYGGPARTNER TRONDHEIM AS?

Tommy Bull is registered as general manager of BYGGPARTNER TRONDHEIM AS.

Where is BYGGPARTNER TRONDHEIM AS based?

BYGGPARTNER TRONDHEIM AS has its business address in Heimdal.

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.