BIZTRAC BETA
COMPANY REGISTER PROFILE
931369431 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

SQUUR HOLDING AS

Org. no. 931369431 Limited company (AS) Lindesnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 48,000
Operating profit NOK 45,000
Equity NOK 60,000
Incorporated 2023
Share capital NOK 30,000

SQUUR HOLDING AS is registered as a limited company in Lindesnes, Agder with organisation number 931369431. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 48,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2024

Revenue
NOK 48,000
Operating profit
NOK 45,000
Equity
NOK 60,000
Est. value
NOK 163,000

Financial health · 2024

Liquidity
1.95
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.7%
Weak
Equity as a share of total capital

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

Who owns SQUUR HOLDING AS?

ESPEN NØDING EKORNRØD
SQUUR HOLDING AS
NOK 48,000 rev. · NOK 45,000 profit

SQUUR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SQUUR HOLDING AS

Who owns SQUUR HOLDING AS?

ESPEN NØDING EKORNRØD is the largest registered owner, with 100.0%.

What is the revenue of SQUUR HOLDING AS?

SQUUR HOLDING AS had revenue of NOK 48,000 in 2024.

Who is the general manager of SQUUR HOLDING AS?

Espen Nøding Ekornrød is registered as general manager of SQUUR HOLDING AS.

Where is SQUUR HOLDING AS based?

SQUUR HOLDING AS has its business address in Holum.

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.