BIZTRAC BETA
Activities of advertising agencies

STRAND MEDIA AND CONSULTING AS

Org. no. 930800171 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 144,000
Equity NOK 131,000
Incorporated 2023
Share capital NOK 30,000

STRAND MEDIA AND CONSULTING AS is registered as a limited company in Asker, Akershus with organisation number 930800171. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av markedsføringstjenester til virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 144,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 144,000
Equity
NOK 131,000
Est. value
NOK 767,000

Financial health · 2025

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

Who owns STRAND MEDIA AND CONSULTING AS?

OLE SVENDSEN STRAND
STRAND MEDIA AND CONSULTING AS
NOK 1.8m rev. · NOK 144,000 profit

STRAND MEDIA AND CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STRAND MEDIA AND CONSULTING AS

Who owns STRAND MEDIA AND CONSULTING AS?

OLE SVENDSEN STRAND is the largest registered owner, with 100.0%.

What is the revenue of STRAND MEDIA AND CONSULTING AS?

STRAND MEDIA AND CONSULTING AS had revenue of NOK 1.8m in 2025.

Who is the general manager of STRAND MEDIA AND CONSULTING AS?

Ole Svendsen Strand is registered as general manager of STRAND MEDIA AND CONSULTING AS.

Where is STRAND MEDIA AND CONSULTING AS based?

STRAND MEDIA AND CONSULTING AS has its business address in Hvalstad.

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.