BIZTRAC BETA
Combined facilities support activities

HTB EIENDOMSERVICE AS

Org. no. 880295322 Limited company (AS) Eidskog Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK −30,000
Equity NOK 272,000
Incorporated 1998
Employees 5
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

HTB EIENDOMSERVICE AS is registered as a limited company in Eidskog, Innlandet with organisation number 880295322. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 1998 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 300 shares. The company's stated purpose is: “Service og vedlikehold innen eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK −30,000
Equity
NOK 272,000
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.2%
Good
Equity as a share of total capital

Who owns HTB EIENDOMSERVICE AS?

BJØRN IVAR SKULSTAD
HTB EIENDOMSERVICE AS
NOK 3.0m rev. · NOK −30,000 profit

HTB EIENDOMSERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HTB EIENDOMSERVICE AS

Who owns HTB EIENDOMSERVICE AS?

BJØRN IVAR SKULSTAD is the largest registered owner, with 88.7%.

What is the revenue of HTB EIENDOMSERVICE AS?

HTB EIENDOMSERVICE AS had revenue of NOK 3.0m in 2024.

Who is the general manager of HTB EIENDOMSERVICE AS?

Bjørn Ivar Skulstad is registered as general manager of HTB EIENDOMSERVICE AS.

Where is HTB EIENDOMSERVICE AS based?

HTB EIENDOMSERVICE AS has its business address in Matrand.

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.