BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER IVAR KJOBERG AS

Org. no. 917421021 Limited company (AS) Ullensvang Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 2.9m
Operating profit NOK 253,000
Equity NOK 487,000
Incorporated 2016
Share capital NOK 30,000

BYGGMESTER IVAR KJOBERG AS is registered as a limited company in Ullensvang, Vestland with organisation number 917421021. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av byggevarer og snekkertjenester samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.9m in revenue and NOK 253,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.9m
Operating profit
NOK 253,000
Equity
NOK 487,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns BYGGMESTER IVAR KJOBERG AS?

IVAR KJOBERG
BYGGMESTER IVAR KJOBERG AS
NOK 2.9m rev. · NOK 253,000 profit

BYGGMESTER IVAR KJOBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER IVAR KJOBERG AS

Who owns BYGGMESTER IVAR KJOBERG AS?

IVAR KJOBERG is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER IVAR KJOBERG AS?

BYGGMESTER IVAR KJOBERG AS had revenue of NOK 2.9m in 2025.

Who is the general manager of BYGGMESTER IVAR KJOBERG AS?

Ivar Kjoberg is registered as general manager of BYGGMESTER IVAR KJOBERG AS.

Where is BYGGMESTER IVAR KJOBERG AS based?

BYGGMESTER IVAR KJOBERG AS has its business address in Nå.

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.