BIZTRAC BETA
COMPANY REGISTER PROFILE
990689741 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

BILSENTERET EIENDOM HESTMARKA AS

Org. no. 990689741 Limited company (AS) Namsos Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 2.6m
Equity NOK 6.0m
Incorporated 2006
Share capital NOK 7.1m

BILSENTERET EIENDOM HESTMARKA AS is registered as a limited company in Namsos, Trøndelag with organisation number 990689741. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 7.1m, divided into 284 shares. The company's stated purpose is: “Erverv og leie ut eiendommer, samt ved aksjer eller på annen måte delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
▲ +11 %
Operating profit
NOK 2.6m
▲ +81 %
Equity
NOK 6.0m
▲ +1 %
Est. value
NOK 7.7m

Financial health · 2025

Liquidity
3.49
Very good
Current assets ÷ current liabilities
Profitability
5.8%
Weak
Return on total assets
Solidity
13.7%
Satisfactory
Equity as a share of total capital

Who owns BILSENTERET EIENDOM HESTMARKA AS?

BILSENTERET EIENDOM HESTMARKA AS
NOK 5.8m rev. · NOK 2.6m profit

BILSENTERET EIENDOM HESTMARKA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILSENTERET EIENDOM HESTMARKA AS

Who owns BILSENTERET EIENDOM HESTMARKA AS?

BILSENTERET INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BILSENTERET EIENDOM HESTMARKA AS?

BILSENTERET EIENDOM HESTMARKA AS had revenue of NOK 5.8m in 2025.

Where is BILSENTERET EIENDOM HESTMARKA AS based?

BILSENTERET EIENDOM HESTMARKA AS has its business address in Namsos.

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

Report a problem

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