BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER OLE FREDHEIM AS

Org. no. 997097947 Limited company (AS) Evje Og Hornnes Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 129,000
Equity NOK 4,000
Incorporated 2011
Share capital NOK 100,000

BYGGMESTER OLE FREDHEIM AS is registered as a limited company in Evje Og Hornnes, Agder with organisation number 997097947. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Snekkerarbeid, servicetjenester, investeringer og deltagelse i andre selskaper og eiendom, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 129,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 129,000
Equity
NOK 4,000
Est. value
NOK 440,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BYGGMESTER OLE FREDHEIM AS?

OLE FREDHEIM
BYGGMESTER OLE FREDHEIM AS
NOK 2.2m rev. · NOK 129,000 profit

BYGGMESTER OLE FREDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER OLE FREDHEIM AS

Who owns BYGGMESTER OLE FREDHEIM AS?

OLE FREDHEIM is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER OLE FREDHEIM AS?

BYGGMESTER OLE FREDHEIM AS had revenue of NOK 2.2m in 2025.

Where is BYGGMESTER OLE FREDHEIM AS based?

BYGGMESTER OLE FREDHEIM AS has its business address in Evje.

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.