BIZTRAC BETA
Construction of residential and non-residential buildings

HOEL & FJUK HÅNDVERK AS

Org. no. 993769932 Limited company (AS) Lillestrøm Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 29.6m
Operating profit NOK 2.4m
Equity NOK 8.4m
Incorporated 2009
Employees 13
Share capital NOK 100,000

HOEL & FJUK HÅNDVERK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 993769932. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2009 and has 13 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er er snekkerivirksomhet og oppføring av bygninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 29.6m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 29.6m
Operating profit
NOK 2.4m
Equity
NOK 8.4m
Est. value
NOK 12.3m

Financial health · 2025

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

Who owns HOEL & FJUK HÅNDVERK AS?

KAI HELGE EID FJUK
HOEL & FJUK HÅNDVERK AS
NOK 29.6m rev. · NOK 2.4m profit

HOEL & FJUK HÅNDVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOEL & FJUK HÅNDVERK AS

Who owns HOEL & FJUK HÅNDVERK AS?

KAI HELGE EID FJUK is the largest registered owner, with 50.0%.

What is the revenue of HOEL & FJUK HÅNDVERK AS?

HOEL & FJUK HÅNDVERK AS had revenue of NOK 29.6m in 2025.

Who is the general manager of HOEL & FJUK HÅNDVERK AS?

Michael Hoel is registered as general manager of HOEL & FJUK HÅNDVERK AS.

Where is HOEL & FJUK HÅNDVERK AS based?

HOEL & FJUK HÅNDVERK AS has its business address in Blaker.

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.