BIZTRAC BETA
Business and other management consultancy activities

SLAVIN AS

Org. no. 928453308 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 20,000
Operating profit NOK 17,000
Equity NOK 65,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-30 Adresseendring registrert 2026-06-30.

SLAVIN AS is registered as a limited company in Bergen, Vestland with organisation number 928453308. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendom, og å yte rådgivnings og konsulent tjenester innen økonomi og regnskap samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 20,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 20,000
Operating profit
NOK 17,000
Equity
NOK 65,000
Est. value
NOK 81,000

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.3%
Weak
Equity as a share of total capital

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

Who owns SLAVIN AS?

VINJAR SLÅTTEN
SLAVIN AS
NOK 20,000 rev. · NOK 17,000 profit

SLAVIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SLAVIN AS own?

SLAVIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SLAVIN AS

Who owns SLAVIN AS?

VINJAR SLÅTTEN is the largest registered owner, with 100.0%.

What is the revenue of SLAVIN AS?

SLAVIN AS had revenue of NOK 20,000 in 2024.

Where is SLAVIN AS based?

SLAVIN AS has its business address in Bergen.

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.