BIZTRAC BETA
Business and other management consultancy activities

VISTEECA PARTNERS AS

Org. no. 928697347 Limited company (AS) Vestby Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −37,000
Equity NOK 278,000
Incorporated 2021
Share capital NOK 60,000

Signals

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

VISTEECA PARTNERS AS is registered as a limited company in Vestby, Akershus with organisation number 928697347. 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 60,000, divided into 10 shares. The company's stated purpose is: “Konsulenttjenester, import og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −37,000
Equity
NOK 278,000
Est. value
NOK 452,000

Financial health · 2025

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

Who owns VISTEECA PARTNERS AS?

CARSTEN STEENMARK
VISTEECA PARTNERS AS
NOK 0 rev. · NOK −37,000 profit

VISTEECA PARTNERS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VISTEECA PARTNERS AS own?

VISTEECA PARTNERS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VISTEECA PARTNERS AS

Who owns VISTEECA PARTNERS AS?

CARSTEN STEENMARK is the largest registered owner, with 100.0%.

What is the revenue of VISTEECA PARTNERS AS?

VISTEECA PARTNERS AS had revenue of NOK 0 in 2025.

Where is VISTEECA PARTNERS AS based?

VISTEECA PARTNERS AS has its business address in Vestby.

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.