biztrac. BETA
COMPANY REGISTER PROFILE
927074958 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

WULLUMSTAD EIENDOM AS

Org. no. 927074958 Limited company (AS) Namsos Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 184,000
Operating profit NOK 22,000
Equity NOK 212,000
Incorporated 2021
Share capital NOK 400,000

WULLUMSTAD EIENDOM AS is registered as a limited company in Namsos, Trøndelag with organisation number 927074958. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Kjøp, salg, utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 184,000 in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 184,000
▼ −88 %
Operating profit
NOK 22,000
▼ −90 %
Equity
NOK 212,000
▼ −15 %
Est. value
NOK 286,000

Financial health · 2025

Liquidity
4.64
Very good
Current assets ÷ current liabilities
Profitability
1.1%
Weak
Return on total assets
Solidity
6.9%
Weak
Equity as a share of total capital

Who owns WULLUMSTAD EIENDOM AS?

WULLUMSTAD EIENDOM AS
NOK 184,000 rev. · NOK 22,000 profit

WULLUMSTAD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WULLUMSTAD EIENDOM AS

Who owns WULLUMSTAD EIENDOM AS?

Reinert Sæternes is the largest registered owner, with 50.0%.

What is the revenue of WULLUMSTAD EIENDOM AS?

WULLUMSTAD EIENDOM AS had revenue of NOK 184,000 in 2025.

Who is the general manager of WULLUMSTAD EIENDOM AS?

Reinert Sæternes is registered as general manager of WULLUMSTAD EIENDOM AS.

Where is WULLUMSTAD EIENDOM AS based?

WULLUMSTAD EIENDOM AS has its business address in Spillum.

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.