BIZTRAC BETA
Rental and operating of own or leased real estate

J H INVEST AS

Org. no. 936676200 Limited company (AS) Stad Incorporated 1985 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 2.4m
Equity NOK 35.5m
Incorporated 1985
Share capital NOK 250,000

J H INVEST AS is registered as a limited company in Stad, Vestland with organisation number 936676200. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1985. Registered share capital is NOK 250,000. The company's stated purpose is: “Entreprenørvirksomhet og utleige av maskiner samt hva som herved står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 2.4m
Equity
NOK 35.5m
Est. value
NOK 30.8m

Financial health · 2024

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

Who owns J H INVEST AS?

JARLE SVEIN HONNINGSVÅG
J H INVEST AS
NOK 3.3m rev. · NOK 2.4m profit

J H INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does J H INVEST AS own?

J H INVEST AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about J H INVEST AS

Who owns J H INVEST AS?

JARLE SVEIN HONNINGSVÅG is the largest registered owner, with 100.0%.

What is the revenue of J H INVEST AS?

J H INVEST AS had revenue of NOK 3.3m in 2024.

Who is the general manager of J H INVEST AS?

Johnny Norvald Birknes is registered as general manager of J H INVEST AS.

Where is J H INVEST AS based?

J H INVEST AS has its business address in Stadlandet.

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.