biztrac. BETA
COMPANY REGISTER PROFILE
938334366 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

HELGE FRØILAND AS

Org. no. 938334366 Limited company (AS) Drammen Incorporated 1985 Active
Revenue 2025 NOK 0
Operating profit NOK −35,000
Equity NOK 3.2m
Incorporated 1985
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

HELGE FRØILAND AS is registered as a limited company in Drammen, Buskerud with organisation number 938334366. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1985. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Produksjon og salg. ”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35,000
▼ −132 %
Equity
NOK 3.2m
▼ −0 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
2.2%
Weak
Return on total assets
Solidity
40.3%
Very good
Equity as a share of total capital

Who owns HELGE FRØILAND AS?

HELGE FRØILAND AS
NOK 0 rev. · NOK −35,000 profit

HELGE FRØILAND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HELGE FRØILAND AS own?

HELGE FRØILAND AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HELGE FRØILAND AS

Who owns HELGE FRØILAND AS?

Helge Frøiland is the largest registered owner, with 100.0%.

What is the revenue of HELGE FRØILAND AS?

HELGE FRØILAND AS had revenue of NOK 0 in 2025.

Where is HELGE FRØILAND AS based?

HELGE FRØILAND AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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