BIZTRAC BETA
Rental and operating of own or leased real estate

BORGEDAL BYGG EIENDOM AS

Org. no. 929125223 Limited company (AS) Ringebu Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 540,000
Operating profit NOK 272,000
Equity NOK 525,000
Incorporated 2022
Share capital NOK 50,000

BORGEDAL BYGG EIENDOM AS is registered as a limited company in Ringebu, Innlandet with organisation number 929125223. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt drive virksomhet i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 540,000 in revenue and NOK 272,000 in operating profit.

Key figures · 2025

Revenue
NOK 540,000
Operating profit
NOK 272,000
Equity
NOK 525,000
Est. value
NOK 632,000

Financial health · 2025

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

Who owns BORGEDAL BYGG EIENDOM AS?

BORGEDAL BYGG AS
BORGEDAL BYGG EIENDOM AS
NOK 540,000 rev. · NOK 272,000 profit

BORGEDAL BYGG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGEDAL BYGG EIENDOM AS

Who owns BORGEDAL BYGG EIENDOM AS?

BORGEDAL BYGG AS is the largest registered owner, with 100.0%.

What is the revenue of BORGEDAL BYGG EIENDOM AS?

BORGEDAL BYGG EIENDOM AS had revenue of NOK 540,000 in 2025.

Who is the general manager of BORGEDAL BYGG EIENDOM AS?

Tor Sverre Borgedal is registered as general manager of BORGEDAL BYGG EIENDOM AS.

Where is BORGEDAL BYGG EIENDOM AS based?

BORGEDAL BYGG EIENDOM AS has its business address in Fåvang.

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.