BIZTRAC BETA
Construction of residential and non-residential buildings

HTP ENTREPRENØR AS

Org. no. 931398407 Limited company (AS) Indre Østfold Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 118,000
Equity NOK 152,000
Incorporated 2023
Share capital NOK 30,000

HTP ENTREPRENØR AS is registered as a limited company in Indre Østfold, Østfold with organisation number 931398407. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Håndverktjenester (snekker, maler), teknisk og prosjekt. Samt å delta i annen spesialisert bygge og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 118,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 118,000
Equity
NOK 152,000
Est. value
NOK 379,000

Financial health · 2025

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

Who owns HTP ENTREPRENØR AS?

DINAS PALIJANSKAS
HTP ENTREPRENØR AS
NOK 4.3m rev. · NOK 118,000 profit

HTP ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HTP ENTREPRENØR AS

Who owns HTP ENTREPRENØR AS?

DINAS PALIJANSKAS is the largest registered owner, with 100.0%.

What is the revenue of HTP ENTREPRENØR AS?

HTP ENTREPRENØR AS had revenue of NOK 4.3m in 2024.

Who is the general manager of HTP ENTREPRENØR AS?

Dinas Palijanskas is registered as general manager of HTP ENTREPRENØR AS.

Where is HTP ENTREPRENØR AS based?

HTP ENTREPRENØR AS has its business address in Mysen.

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.