BIZTRAC BETA
Architectural activities

SIVILARKITEKT LEIF LARSEN HOLDING AS

Org. no. 989254405 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −29,000
Equity NOK 11.6m
Incorporated 2005
Share capital NOK 100,000

Signals

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

SIVILARKITEKT LEIF LARSEN HOLDING AS is registered as a limited company in Sandnes, Rogaland with organisation number 989254405. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i verdipapirer, samt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −29,000
Equity
NOK 11.6m
Est. value
NOK 18.3m

Financial health · 2025

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

Who owns SIVILARKITEKT LEIF LARSEN HOLDING AS?

LEIF ODDVARD LARSEN
SIVILARKITEKT LEIF LARSEN HOLDING AS
· NOK −29,000 profit

SIVILARKITEKT LEIF LARSEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIVILARKITEKT LEIF LARSEN HOLDING AS own?

SIVILARKITEKT LEIF LARSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIVILARKITEKT LEIF LARSEN HOLDING AS

Who owns SIVILARKITEKT LEIF LARSEN HOLDING AS?

LEIF ODDVARD LARSEN is the largest registered owner, with 100.0%.

Who is the general manager of SIVILARKITEKT LEIF LARSEN HOLDING AS?

Leif Oddvard Larsen is registered as general manager of SIVILARKITEKT LEIF LARSEN HOLDING AS.

Where is SIVILARKITEKT LEIF LARSEN HOLDING AS based?

SIVILARKITEKT LEIF LARSEN HOLDING AS has its business address in Sandnes.

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.