BIZTRAC BETA
General cleaning of buildings

J. E. HALVORSEN AS

Org. no. 986478663 Limited company (AS) Lørenskog Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 606,000
Equity NOK 835,000
Incorporated 2004
Share capital NOK 100,000

J. E. HALVORSEN AS is registered as a limited company in Lørenskog, Akershus with organisation number 986478663. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Yte tjenester innenfor renhold og vaktmesterservice, samt å investere i aksjer og obligasjoner, erverve og forvalte faste eiendommer samt å yte lån eller garantier for lån samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 606,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 606,000
Equity
NOK 835,000
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns J. E. HALVORSEN AS?

J. E. H. INVEST AS
J. E. HALVORSEN AS
NOK 1.2m rev. · NOK 606,000 profit

J. E. HALVORSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about J. E. HALVORSEN AS

Who owns J. E. HALVORSEN AS?

J. E. H. INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of J. E. HALVORSEN AS?

J. E. HALVORSEN AS had revenue of NOK 1.2m in 2025.

Who is the general manager of J. E. HALVORSEN AS?

John Erik Halvorsen is registered as general manager of J. E. HALVORSEN AS.

Where is J. E. HALVORSEN AS based?

J. E. HALVORSEN AS has its business address in Fjellhamar.

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.