BIZTRAC BETA
Raising of dairy cattle

JENSEN MASKINDRIFT DYREHOLD AS

Org. no. 935922496 Limited company (AS) Sel Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 132,000
Operating profit NOK 241,000
Equity NOK 225,000
Incorporated 2025
Share capital NOK 30,000

JENSEN MASKINDRIFT DYREHOLD AS is registered as a limited company in Sel, Innlandet with organisation number 935922496. The business is classified under raising of dairy cattle (NACE 01.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Leiekjøring innenfor landbruk, melk og kjøttproduskjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 132,000 in revenue and NOK 241,000 in operating profit.

Key figures · 2025

Revenue
NOK 132,000
Operating profit
NOK 241,000
Equity
NOK 225,000
Est. value
NOK 726,000

Financial health · 2025

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

Who owns JENSEN MASKINDRIFT DYREHOLD AS?

SEBASTIAN ASPELUND JENSEN
JENSEN MASKINDRIFT DYREHOLD AS
NOK 132,000 rev. · NOK 241,000 profit

JENSEN MASKINDRIFT DYREHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JENSEN MASKINDRIFT DYREHOLD AS

Who owns JENSEN MASKINDRIFT DYREHOLD AS?

SEBASTIAN ASPELUND JENSEN is the largest registered owner, with 100.0%.

What is the revenue of JENSEN MASKINDRIFT DYREHOLD AS?

JENSEN MASKINDRIFT DYREHOLD AS had revenue of NOK 132,000 in 2025.

Who is the general manager of JENSEN MASKINDRIFT DYREHOLD AS?

Sebastian Aspelund Jensen is registered as general manager of JENSEN MASKINDRIFT DYREHOLD AS.

Where is JENSEN MASKINDRIFT DYREHOLD AS based?

JENSEN MASKINDRIFT DYREHOLD AS has its business address in Heidal.

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.