BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ADAMS BUTIKK AS

Org. no. 922437688 Limited company (AS) Nittedal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 36.7m
Operating profit NOK 464,000
Equity NOK 1.5m
Incorporated 2019
Share capital NOK 350,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ADAMS BUTIKK AS is registered as a limited company in Nittedal, Akershus with organisation number 922437688. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2019. Registered share capital is NOK 350,000, divided into 100 shares. The company's stated purpose is: “Dagligvarehandel og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 36.7m in revenue and NOK 464,000 in operating profit.

Key figures · 2024

Revenue
NOK 36.7m
Operating profit
NOK 464,000
Equity
NOK 1.5m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns ADAMS BUTIKK AS?

ADAM LASKOWSKI
ADAMS BUTIKK AS
NOK 36.7m rev. · NOK 464,000 profit

ADAMS BUTIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADAMS BUTIKK AS own?

ADAMS BUTIKK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ADAMS BUTIKK AS

Who owns ADAMS BUTIKK AS?

ADAM LASKOWSKI is the largest registered owner, with 100.0%.

What is the revenue of ADAMS BUTIKK AS?

ADAMS BUTIKK AS had revenue of NOK 36.7m in 2024.

Where is ADAMS BUTIKK AS based?

ADAMS BUTIKK AS has its business address in Hagan.

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.