BIZTRAC BETA
COMPANY REGISTER PROFILE
993406252 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities in reception centres for asylum seekers

SMIA EIENDOM DB AS

Org. no. 993406252 Limited company (AS) Hadsel Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 809,000
Equity NOK 791,000
Incorporated 2008
Share capital NOK 1.1m

SMIA EIENDOM DB AS is registered as a limited company in Hadsel, Nordland with organisation number 993406252. The business is classified under activities in reception centres for asylum seekers (NACE 87.992). The company was incorporated in 2008. Registered share capital is NOK 1.1m, divided into 2100 shares. The company's stated purpose is: “Selskapets formål er utleie av leiligheter og forretningseiendommer, samt annet som faller naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 809,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 809,000
Equity
NOK 791,000
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns SMIA EIENDOM DB AS?

SMIA EIENDOM DB AS
NOK 1.7m rev. · NOK 809,000 profit

SMIA EIENDOM DB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMIA EIENDOM DB AS

Who owns SMIA EIENDOM DB AS?

MOTTAK NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of SMIA EIENDOM DB AS?

SMIA EIENDOM DB AS had revenue of NOK 1.7m in 2025.

Who is the general manager of SMIA EIENDOM DB AS?

Sami Hajzeri is registered as general manager of SMIA EIENDOM DB AS.

Where is SMIA EIENDOM DB AS based?

SMIA EIENDOM DB AS has its business address in Melbu.

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.