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

LAYCOCK HOLDING AS

Org. no. 930818828 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 243,000
Incorporated 2023
Share capital NOK 250,000

Signals

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

LAYCOCK HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 930818828. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 250,000, divided into 250000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −4,000
Equity
NOK 243,000
Est. value
NOK 285,000

Financial health · 2024

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

Who owns LAYCOCK HOLDING AS?

AIMEE ELIZABETH LAYCOCK
LAYCOCK HOLDING AS
· NOK −4,000 profit

LAYCOCK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAYCOCK HOLDING AS own?

LAYCOCK HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LAYCOCK HOLDING AS

Who owns LAYCOCK HOLDING AS?

AIMEE ELIZABETH LAYCOCK is the largest registered owner, with 100.0%.

Who is the general manager of LAYCOCK HOLDING AS?

Aimee Elizabeth Laycock is registered as general manager of LAYCOCK HOLDING AS.

Where is LAYCOCK HOLDING AS based?

LAYCOCK 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.