BIZTRAC BETA
Development of building projects

KYRKJESTØYL HYTTEBYGG AS

Org. no. 917512795 Limited company (AS) Grimstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 27,000
Operating profit NOK −172,000
Equity NOK 1.8m
Incorporated 2016
Share capital NOK 4.7m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−172k kr).

KYRKJESTØYL HYTTEBYGG AS is registered as a limited company in Grimstad, Agder with organisation number 917512795. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 4.7m, divided into 1110 shares. The company's stated purpose is: “Kjøp, utvikling og salg av hyttetomter og hytter. Grunn- og byggearbeid på egen og andres eiendom, samt utleie av personell og maskiner til dette. Tilhørende virksomhet, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 27,000 in revenue and NOK −172,000 in operating profit.

Key figures · 2024

Revenue
NOK 27,000
Operating profit
NOK −172,000
Equity
NOK 1.8m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns KYRKJESTØYL HYTTEBYGG AS?

TOMSTAD AS
KYRKJESTØYL HYTTEBYGG AS
NOK 27,000 rev. · NOK −172,000 profit

KYRKJESTØYL HYTTEBYGG AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KYRKJESTØYL HYTTEBYGG AS

Who owns KYRKJESTØYL HYTTEBYGG AS?

TOMSTAD AS is the largest registered owner, with 55.0%.

What is the revenue of KYRKJESTØYL HYTTEBYGG AS?

KYRKJESTØYL HYTTEBYGG AS had revenue of NOK 27,000 in 2024.

Where is KYRKJESTØYL HYTTEBYGG AS based?

KYRKJESTØYL HYTTEBYGG AS has its business address in Grimstad.

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.