BIZTRAC BETA
Other business support service activities n.e.c.

VINSENTRALEN AS

Org. no. 812802372 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −596,000
Incorporated 2013
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−596k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VINSENTRALEN AS is registered as a limited company in Oslo, Oslo with organisation number 812802372. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor mat og drikke, samt medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −596,000

Financial health · 2025

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

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

Who owns VINSENTRALEN AS?

REGNSKAPSHUSET AS
VINSENTRALEN AS
NOK 0 rev. · NOK 0 profit

VINSENTRALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINSENTRALEN AS

Who owns VINSENTRALEN AS?

REGNSKAPSHUSET AS is the largest registered owner, with 100.0%.

What is the revenue of VINSENTRALEN AS?

VINSENTRALEN AS had revenue of NOK 0 in 2025.

Where is VINSENTRALEN AS based?

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