BIZTRAC BETA
COMPANY REGISTER PROFILE
928318834 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LEFKADA AS

Org. no. 928318834 Limited company (AS) Sveio Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK 2.5m
Incorporated 2021
Share capital NOK 30,000

Signals

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

LEFKADA AS is registered as a limited company in Sveio, Vestland with organisation number 928318834. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investering i aksjer og andeler innenfor takbransjen samt alt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −22,000
▼ −18 %
Equity
NOK 2.5m
▲ +19 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
631.82
Very good
Current assets ÷ current liabilities
Profitability
17.7%
Very good
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns LEFKADA AS?

LEFKADA AS
· NOK −22,000 profit

LEFKADA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEFKADA AS own?

LEFKADA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEFKADA AS

Who owns LEFKADA AS?

HELENE NYGÅRD is the largest registered owner, with 100.0%.

Where is LEFKADA AS based?

LEFKADA AS has its business address in Sveio.

Property

Business address Nygårdsvegen 51, 5550 Sveio
Cadastral unit 4612-41/71/0/0
Building Enebolig · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.