biztrac. BETA
COMPANY REGISTER PROFILE
922331561 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

BTHS EIENDOM AS

Org. no. 922331561 Limited company (AS) Elverum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 344,000
Equity NOK 2.1m
Incorporated 2019
Share capital NOK 30,000

BTHS EIENDOM AS is registered as a limited company in Elverum, Innlandet with organisation number 922331561. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å eie, forvalte og investere i fast eiendom, samt drive annen tilhørende virksomhet. Selskapet kan ha eierinteresser i andre selskaper som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 344,000 in operating profit.

Former names: ALFANOR 19120 AS

Key figures · 2025

Revenue
NOK 1.5m
▲ +2 %
Operating profit
NOK 344,000
▲ +6 %
Equity
NOK 2.1m
▲ +15 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
18.21
Very good
Current assets ÷ current liabilities
Profitability
1.5%
Weak
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns BTHS EIENDOM AS?

BTHS EIENDOM AS
NOK 1.5m rev. · NOK 344,000 profit

BTHS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BTHS EIENDOM AS

Who owns BTHS EIENDOM AS?

TOR HARALD SVENDSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BTHS EIENDOM AS?

BTHS EIENDOM AS had revenue of NOK 1.5m in 2025.

Where is BTHS EIENDOM AS based?

BTHS EIENDOM AS has its business address in Elverum.

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

Report a problem

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