BIZTRAC BETA
Construction of residential and non-residential buildings

H J OFTEDAL AS

Org. no. 918094288 Limited company (AS) Time Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK 1.1m
Equity NOK 2.0m
Incorporated 2016
Share capital NOK 30,000

H J OFTEDAL AS is registered as a limited company in Time, Rogaland with organisation number 918094288. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i aksjer og andre verdipapirer, herunder å delta i andre virksomheter, handel og dertil tilhørende virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK 1.1m
Equity
NOK 2.0m
Est. value
NOK 4.3m

Financial health · 2024

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

Who owns H J OFTEDAL AS?

HELGE JOHAN OFTEDAL
H J OFTEDAL AS
NOK 7.3m rev. · NOK 1.1m profit

H J OFTEDAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does H J OFTEDAL AS own?

H J OFTEDAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about H J OFTEDAL AS

Who owns H J OFTEDAL AS?

HELGE JOHAN OFTEDAL is the largest registered owner, with 100.0%.

What is the revenue of H J OFTEDAL AS?

H J OFTEDAL AS had revenue of NOK 7.3m in 2024.

Who is the general manager of H J OFTEDAL AS?

Helge Johan Oftedal is registered as general manager of H J OFTEDAL AS.

Where is H J OFTEDAL AS based?

H J OFTEDAL AS has its business address in Bryne.

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.