BIZTRAC BETA
Retail sale of pharmaceutical products

LAPPOTEKET AS

Org. no. 989228765 Limited company (AS) Vik Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −34,000
Equity NOK 11.2m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−34k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LAPPOTEKET AS is registered as a limited company in Vik, Vestland with organisation number 989228765. The business is classified under retail sale of pharmaceutical products (NACE 47.730). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og selskapsandeler samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −34,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −34,000
Equity
NOK 11.2m
Est. value
NOK 16.6m

Financial health · 2024

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

Who owns LAPPOTEKET AS?

BRITA A FOSSE
LAPPOTEKET AS
NOK 0 rev. · NOK −34,000 profit

LAPPOTEKET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAPPOTEKET AS own?

LAPPOTEKET AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LAPPOTEKET AS

Who owns LAPPOTEKET AS?

BRITA A FOSSE is the largest registered owner, with 100.0%.

What is the revenue of LAPPOTEKET AS?

LAPPOTEKET AS had revenue of NOK 0 in 2024.

Where is LAPPOTEKET AS based?

LAPPOTEKET AS has its business address in Vik I Sogn.

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.