BIZTRAC BETA
Wholesale of metals and metal ores

A JENSERUD & SØNN AS

Org. no. 865626002 Limited company (AS) Gran Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 37.6m
Operating profit NOK −3.7m
Equity NOK 3.4m
Incorporated 1992
Employees 25
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,7 mill kr).

A JENSERUD & SØNN AS is registered as a limited company in Gran, Innlandet with organisation number 865626002. The business is classified under wholesale of metals and metal ores (NACE 46.820). The company was incorporated in 1992 and has 25 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Kjøp, salg og legging av jern, samt virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.6m in revenue and NOK −3.7m in operating profit.

Key figures · 2024

Revenue
NOK 37.6m
Operating profit
NOK −3.7m
Equity
NOK 3.4m
Est. value
NOK 13.9m

Financial health · 2024

Liquidity
0.84
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.9%
Good
Equity as a share of total capital

Who owns A JENSERUD & SØNN AS?

JENSERUD HOLDING AS
A JENSERUD & SØNN AS
NOK 37.6m rev. · NOK −3.7m profit

A JENSERUD & SØNN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about A JENSERUD & SØNN AS

Who owns A JENSERUD & SØNN AS?

JENSERUD HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of A JENSERUD & SØNN AS?

A JENSERUD & SØNN AS had revenue of NOK 37.6m in 2024.

Who is the general manager of A JENSERUD & SØNN AS?

Frode Jenserud is registered as general manager of A JENSERUD & SØNN AS.

Where is A JENSERUD & SØNN AS based?

A JENSERUD & SØNN AS has its business address in Jaren.

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.