biztrac. BETA
COMPANY REGISTER PROFILE
915870627 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

RAULAND HYTTEBYGG AS

Org. no. 915870627 Limited company (AS) Vinje Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −233,000
Equity NOK −641,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−641k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−233k kr).

RAULAND HYTTEBYGG AS is registered as a limited company in Vinje, Telemark with organisation number 915870627. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utvikling og salg av fast eiendom, herunder oppføring av fritidseiendommer, eie aksjer i andre selskap, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −233,000
▲ +91 %
Equity
NOK −641,000
▼ −254 %

Financial health · 2025

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-5.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns RAULAND HYTTEBYGG AS?

RAULAND HYTTEBYGG AS
· NOK −233,000 profit

RAULAND HYTTEBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAULAND HYTTEBYGG AS

Who owns RAULAND HYTTEBYGG AS?

SVALASTOG HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of RAULAND HYTTEBYGG AS?

Erling Svalastog is registered as general manager of RAULAND HYTTEBYGG AS.

Where is RAULAND HYTTEBYGG AS based?

RAULAND HYTTEBYGG AS has its business address in Rauland.

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.