BIZTRAC BETA
Development of building projects

SILUR HOLDING AS

Org. no. 919294671 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −137,000
Equity NOK 1.4m
Incorporated 2017
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−137k kr).

SILUR HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 919294671. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 40,000, divided into 30000 shares. The company's stated purpose is: “Drive eiendomsutvikling og utleie og salg av fast eiendom, samt annen virksomhet som naturlig faller inn under dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −137,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −137,000
Equity
NOK 1.4m
Est. value
NOK 1.9m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.3%
Weak
Equity as a share of total capital

Who owns SILUR HOLDING AS?

VÆKERØ INVEST AS
SILUR HOLDING AS
NOK 2.4m rev. · NOK −137,000 profit

SILUR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILUR HOLDING AS

Who owns SILUR HOLDING AS?

VÆKERØ INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SILUR HOLDING AS?

SILUR HOLDING AS had revenue of NOK 2.4m in 2024.

Who is the general manager of SILUR HOLDING AS?

Martin Stuart Gaze is registered as general manager of SILUR HOLDING AS.

Where is SILUR HOLDING AS based?

SILUR HOLDING AS has its business address in Oslo.

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.