BIZTRAC BETA
COMPANY REGISTER PROFILE
964269084 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

HYNI BYGG AS

Org. no. 964269084 Limited company (AS) Skien Incorporated 1992 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 20,000
Equity NOK 801,000
Incorporated 1992
Share capital NOK 100,000

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 2025 financial year, show NOK 1.5m in revenue and NOK 20,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▲ +135 %
Operating profit
NOK 20,000
▲ +130 %
Equity
NOK 801,000
▲ +3 %
Est. value
NOK 468,000

Financial health · 2025

Liquidity
5.80
Very good
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
79.2%
Very good
Equity as a share of total capital

Who owns HYNI BYGG AS?

HYNI BYGG AS
NOK 1.5m rev. · NOK 20,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 1.5m in 2025.

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 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.