BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER BORGE AS

Org. no. 924791098 Limited company (AS) Fedje Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.8m
Operating profit NOK 573,000
Equity NOK 906,000
Incorporated 2020
Share capital NOK 30,000

BYGGMESTER BORGE AS is registered as a limited company in Fedje, Vestland with organisation number 924791098. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Byggebransjen, tømrertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.8m in revenue and NOK 573,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.8m
Operating profit
NOK 573,000
Equity
NOK 906,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns BYGGMESTER BORGE AS?

JAN ERLING BORGE
BYGGMESTER BORGE AS
NOK 6.8m rev. · NOK 573,000 profit

BYGGMESTER BORGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BYGGMESTER BORGE AS own?

BYGGMESTER BORGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BYGGMESTER BORGE AS

Who owns BYGGMESTER BORGE AS?

JAN ERLING BORGE is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER BORGE AS?

BYGGMESTER BORGE AS had revenue of NOK 6.8m in 2025.

Who is the general manager of BYGGMESTER BORGE AS?

Jan Erling Borge is registered as general manager of BYGGMESTER BORGE AS.

Where is BYGGMESTER BORGE AS based?

BYGGMESTER BORGE AS has its business address in Fedje.

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.