BIZTRAC BETA
Architectural activities

SEKVENS HOLDING AS

Org. no. 931920766 Limited company (AS) Hamar Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 10,000
Incorporated 2023
Share capital NOK 40,000

Signals

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

SEKVENS HOLDING AS is registered as a limited company in Hamar, Innlandet with organisation number 931920766. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper av enhver art, herunder også eiendomsaksjeselskap. I tillegg skal selskapet kunne drive virksomhet med kjøp og salg og utleie av fast eiendom samt alt som naturlig hører med til dette. Selskapet kan gi gaver og bidrag til foreninger og selskaper som bidrar i humanitært, veldedig og/eller sosialt arbeid.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 10,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns SEKVENS HOLDING AS?

ANNA OLETTE EVENSEN
SEKVENS HOLDING AS
· NOK −14,000 profit

SEKVENS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SEKVENS HOLDING AS own?

SEKVENS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEKVENS HOLDING AS

Who owns SEKVENS HOLDING AS?

ANNA OLETTE EVENSEN is the largest registered owner, with 50.0%.

Where is SEKVENS HOLDING AS based?

SEKVENS HOLDING AS has its business address in Hamar.

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.