biztrac. BETA
COMPANY REGISTER PROFILE
931266071 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of construction and civil engineering machinery and equipment

HØRTE MASKIN AS

Org. no. 931266071 Limited company (AS) Lier Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 10.3m
Operating profit NOK 935,000
Equity NOK 2.0m
Incorporated 2023
Share capital NOK 200,000

HØRTE MASKIN AS is registered as a limited company in Lier, Buskerud with organisation number 931266071. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Kjøp og utleie av maskiner og redskap og annen virksomhet som naturlig følger av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.3m in revenue and NOK 935,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.3m
▲ +9 %
Operating profit
NOK 935,000
▼ −26 %
Equity
NOK 2.0m
▲ +58 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
0.79
Weak
Current assets ÷ current liabilities
Profitability
19.4%
Very good
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns HØRTE MASKIN AS?

HØRTE MASKIN AS
NOK 10.3m rev. · NOK 935,000 profit

HØRTE MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØRTE MASKIN AS

Who owns HØRTE MASKIN AS?

HØRTEBONDEN AS is the largest registered owner, with 100.0%.

What is the revenue of HØRTE MASKIN AS?

HØRTE MASKIN AS had revenue of NOK 10.3m in 2025.

Who is the general manager of HØRTE MASKIN AS?

Anders Hørthe is registered as general manager of HØRTE MASKIN AS.

Where is HØRTE MASKIN AS based?

HØRTE MASKIN AS has its business address in Sylling.

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.