BIZTRAC BETA
Rental and operating of own or leased real estate

STENSVOLD SAMEIE AS

Org. no. 931068393 Limited company (AS) Sarpsborg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 445,000
Operating profit NOK 258,000
Equity NOK 843,000
Incorporated 2023
Share capital NOK 60,000

STENSVOLD SAMEIE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 931068393. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom, herunder kjøp, salg og utleie, investering i andre eiendomsselskaper samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 445,000 in revenue and NOK 258,000 in operating profit.

Key figures · 2025

Revenue
NOK 445,000
Operating profit
NOK 258,000
Equity
NOK 843,000
Est. value
NOK 1.0m

Financial health · 2025

Liquidity
7.32
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns STENSVOLD SAMEIE AS?

SIW CHRISTIN BRAATEN
STENSVOLD SAMEIE AS
NOK 445,000 rev. · NOK 258,000 profit

STENSVOLD SAMEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STENSVOLD SAMEIE AS

Who owns STENSVOLD SAMEIE AS?

SIW CHRISTIN BRAATEN is the largest registered owner, with 50.0%.

What is the revenue of STENSVOLD SAMEIE AS?

STENSVOLD SAMEIE AS had revenue of NOK 445,000 in 2025.

Who is the general manager of STENSVOLD SAMEIE AS?

Siw Christin Braaten is registered as general manager of STENSVOLD SAMEIE AS.

Where is STENSVOLD SAMEIE AS based?

STENSVOLD SAMEIE AS has its business address in Klavestadhaugen.

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.