BIZTRAC BETA
Construction of residential and non-residential buildings

HYNI BYGG AS

Org. no. 964269084 Limited company (AS) Skien Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 626,000
Operating profit NOK −66,000
Equity NOK 779,000
Incorporated 1992
Share capital NOK 100,000

Signals

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

HYNI BYGG AS is registered as a limited company in Skien, Telemark with organisation number 964269084. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Handel i bryggebransjen, herunder oppsetting av bygg og underentrepriser og alt som naturlig hører inn under dette, også medvirkning i andre sel- skaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 626,000 in revenue and NOK −66,000 in operating profit.

Key figures · 2024

Revenue
NOK 626,000
Operating profit
NOK −66,000
Equity
NOK 779,000
Est. value
NOK 514,000

Financial health · 2024

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

Who owns HYNI BYGG AS?

KÅRE JAN RAKKESTAD
HYNI BYGG AS
NOK 626,000 rev. · NOK −66,000 profit

HYNI BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HYNI BYGG AS

Who owns HYNI BYGG AS?

KÅRE JAN RAKKESTAD is the largest registered owner, with 100.0%.

What is the revenue of HYNI BYGG AS?

HYNI BYGG AS had revenue of NOK 626,000 in 2024.

Who is the general manager of HYNI BYGG AS?

Kåre Jan Rakkestad is registered as general manager of HYNI BYGG AS.

Where is HYNI BYGG AS based?

HYNI BYGG AS has its business address in Skien.

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.