BIZTRAC BETA
COMPANY REGISTER PROFILE
817238912 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Construction of residential and non-residential buildings

HOSEID AS

Org. no. 817238912 Limited company (AS) Drangedal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 50,000
Operating profit NOK −89,000
Equity NOK 16.8m
Incorporated 2016
Share capital NOK 46,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−89k kr).

HOSEID AS is registered as a limited company in Drangedal, Telemark with organisation number 817238912. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 46,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer og andre andeler i andre selskaper samt det som naturlig er i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 50,000 in revenue and NOK −89,000 in operating profit.

Key figures · 2025

Revenue
NOK 50,000
Operating profit
NOK −89,000
▲ +61 %
Equity
NOK 16.8m
▲ +79 %
Est. value
NOK 69.7m

Financial health · 2025

Liquidity
74.42
Very good
Current assets ÷ current liabilities
Profitability
56.6%
Very good
Return on total assets
Solidity
78.7%
Very good
Equity as a share of total capital

Who owns HOSEID AS?

HOSEID AS
NOK 50,000 rev. · NOK −89,000 profit

HOSEID AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOSEID AS own?

HOSEID AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about HOSEID AS

Who owns HOSEID AS?

OLE AUGUST KARLSEN is the largest registered owner, with 100.0%.

What is the revenue of HOSEID AS?

HOSEID AS had revenue of NOK 50,000 in 2025.

Where is HOSEID AS based?

HOSEID AS has its business address in Drangedal.

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.