BIZTRAC BETA
Rental and operating of own or leased real estate

OPPSANGER INDUSTRIBYGG AS

Org. no. 992421371 Limited company (AS) Kvinnherad Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 356,000
Operating profit NOK 78,000
Equity NOK 865,000
Incorporated 2008
Share capital NOK 1.0m

OPPSANGER INDUSTRIBYGG AS is registered as a limited company in Kvinnherad, Vestland with organisation number 992421371. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i, utvikling og drift av fast eiendom, investering i andre selskap og hva som naturlig hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 356,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2024

Revenue
NOK 356,000
Operating profit
NOK 78,000
Equity
NOK 865,000
Est. value
NOK 726,000

Financial health · 2024

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

Who owns OPPSANGER INDUSTRIBYGG AS?

KVINNVEST AS
OPPSANGER INDUSTRIBYGG AS
NOK 356,000 rev. · NOK 78,000 profit

OPPSANGER INDUSTRIBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OPPSANGER INDUSTRIBYGG AS

Who owns OPPSANGER INDUSTRIBYGG AS?

KVINNVEST AS is the largest registered owner, with 100.0%.

What is the revenue of OPPSANGER INDUSTRIBYGG AS?

OPPSANGER INDUSTRIBYGG AS had revenue of NOK 356,000 in 2024.

Who is the general manager of OPPSANGER INDUSTRIBYGG AS?

Dag Handeland is registered as general manager of OPPSANGER INDUSTRIBYGG AS.

Where is OPPSANGER INDUSTRIBYGG AS based?

OPPSANGER INDUSTRIBYGG AS has its business address in Valen.

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.