BIZTRAC BETA
Buying and selling of own real estate

SVEA BOLIG AS

Org. no. 919982314 Limited company (AS) Lillehammer Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 33,000
Operating profit NOK −263,000
Equity NOK 6,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

SVEA BOLIG AS is registered as a limited company in Lillehammer, Innlandet with organisation number 919982314. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i fast eiendom og aksjer, drift og utleie av fast eiendom og annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 33,000 in revenue and NOK −263,000 in operating profit.

Key figures · 2025

Revenue
NOK 33,000
Operating profit
NOK −263,000
Equity
NOK 6,000
Est. value
NOK 54,000

Financial health · 2025

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

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

Who owns SVEA BOLIG AS?

SKARPSNO AS
SVEA BOLIG AS
NOK 33,000 rev. · NOK −263,000 profit

SVEA BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVEA BOLIG AS

Who owns SVEA BOLIG AS?

SKARPSNO AS is the largest registered owner, with 100.0%.

What is the revenue of SVEA BOLIG AS?

SVEA BOLIG AS had revenue of NOK 33,000 in 2025.

Who is the general manager of SVEA BOLIG AS?

Stian Ryen is registered as general manager of SVEA BOLIG AS.

Where is SVEA BOLIG AS based?

SVEA BOLIG AS has its business address in Lillehammer.

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

Report a problem

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