BIZTRAC BETA
Construction of residential and non-residential buildings

TOTAL BYGGPARTNER AS

Org. no. 916554532 Limited company (AS) Rælingen Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 497,000
Operating profit NOK 147,000
Equity NOK 154,000
Incorporated 2015
Share capital NOK 30,000

TOTAL BYGGPARTNER AS is registered as a limited company in Rælingen, Akershus with organisation number 916554532. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tømrerarbeide og entreprenørvirksomhet, samt deltagelse i andre selskaper ved aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 497,000 in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 497,000
Operating profit
NOK 147,000
Equity
NOK 154,000
Est. value
NOK 513,000

Financial health · 2025

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

Who owns TOTAL BYGGPARTNER AS?

LASSE FRIIS JENSEN
TOTAL BYGGPARTNER AS
NOK 497,000 rev. · NOK 147,000 profit

TOTAL BYGGPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOTAL BYGGPARTNER AS

Who owns TOTAL BYGGPARTNER AS?

LASSE FRIIS JENSEN is the largest registered owner, with 100.0%.

What is the revenue of TOTAL BYGGPARTNER AS?

TOTAL BYGGPARTNER AS had revenue of NOK 497,000 in 2025.

Who is the general manager of TOTAL BYGGPARTNER AS?

Lasse Friis Jensen is registered as general manager of TOTAL BYGGPARTNER AS.

Where is TOTAL BYGGPARTNER AS based?

TOTAL BYGGPARTNER AS has its business address in Fjerdingby.

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.