biztrac. BETA
COMPANY REGISTER PROFILE
919935863 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Hotels and similar accommodation

BYGDIN EIENDOM AS

Org. no. 919935863 Limited company (AS) Øystre Slidre Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −40,000
Equity NOK 3.0m
Incorporated 2017
Share capital NOK 150,000

Signals

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

BYGDIN EIENDOM AS is registered as a limited company in Øystre Slidre, Innlandet with organisation number 919935863. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 2017. Registered share capital is NOK 150,000, divided into 120 shares. The company's stated purpose is: “Investeringsvirksomhet, kjøp og salg, samt utleie av fast eiendom og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −40,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −40,000
▼ −16 %
Equity
NOK 3.0m
▲ +68 %
Est. value
NOK 11.7m

Financial health · 2025

Liquidity
55.12
Very good
Current assets ÷ current liabilities
Profitability
9.7%
Satisfactory
Return on total assets
Solidity
22.7%
Good
Equity as a share of total capital

Who owns BYGDIN EIENDOM AS?

BYGDIN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BYGDIN EIENDOM AS own?

BYGDIN EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BYGDIN EIENDOM AS

Who owns BYGDIN EIENDOM AS?

OXHOVD AS is the largest registered owner, with 50.0%.

What is the revenue of BYGDIN EIENDOM AS?

BYGDIN EIENDOM AS had revenue of NOK 0 in 2025.

Where is BYGDIN EIENDOM AS based?

BYGDIN EIENDOM AS has its business address in Skammestein.

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.