BIZTRAC BETA
Construction of residential and non-residential buildings

KIRKEØY BYGG AS

Org. no. 922767823 Limited company (AS) Hvaler Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.3m
Operating profit NOK 137,000
Equity NOK 561,000
Incorporated 2019
Share capital NOK 30,000

KIRKEØY BYGG AS is registered as a limited company in Hvaler, Østfold with organisation number 922767823. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Byggvirksomhet og andre produkter/tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskap med lignende virksomhet og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.3m in revenue and NOK 137,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.3m
Operating profit
NOK 137,000
Equity
NOK 561,000
Est. value
NOK 661,000

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.5%
Good
Equity as a share of total capital

Who owns KIRKEØY BYGG AS?

LARS ANDRÈ HANES
KIRKEØY BYGG AS
NOK 6.3m rev. · NOK 137,000 profit

KIRKEØY BYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIRKEØY BYGG AS

Who owns KIRKEØY BYGG AS?

LARS ANDRÈ HANES is the largest registered owner, with 45.0%.

What is the revenue of KIRKEØY BYGG AS?

KIRKEØY BYGG AS had revenue of NOK 6.3m in 2025.

Who is the general manager of KIRKEØY BYGG AS?

Petter Høkeli is registered as general manager of KIRKEØY BYGG AS.

Where is KIRKEØY BYGG AS based?

KIRKEØY BYGG AS has its business address in Skjærhalden.

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.