BIZTRAC BETA
Activities of advertising agencies

VISIVO AS

Org. no. 924345861 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 242,000
Equity NOK 61,000
Incorporated 2019
Employees 7
Share capital NOK 30,000

VISIVO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 924345861. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2019 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Markedsføringsbyrå med fokus på å fremme veksten og lønnsomheten til våre kunder gjennom kreative, effektive og innovative strategier. Visivo streber etter å bygge langvarige partnerskap basert på tillit, integritet og gjensidig suksess.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 242,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 242,000
Equity
NOK 61,000
Est. value
NOK 1.2m

Financial health · 2024

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

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

Who owns VISIVO AS?

VISIMOR AS
VISIVO AS
NOK 3.0m rev. · NOK 242,000 profit

VISIVO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VISIVO AS

Who owns VISIVO AS?

VISIMOR AS is the largest registered owner, with 99.0%.

What is the revenue of VISIVO AS?

VISIVO AS had revenue of NOK 3.0m in 2024.

Who is the general manager of VISIVO AS?

Sigurd Østerbø Søbye is registered as general manager of VISIVO AS.

Where is VISIVO AS based?

VISIVO AS has its business address in Lillestrøm.

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.