biztrac. BETA
COMPANY REGISTER PROFILE
980850234 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Market research and public opinion polling

MARKEDSINFO AS

Org. no. 980850234 Limited company (AS) Hamar Incorporated 1999 Active
Revenue 2024 NOK 4.9m
Operating profit NOK 181,000
Equity NOK 324,000
Incorporated 1999
Share capital NOK 350,000

MARKEDSINFO AS is registered as a limited company in Hamar, Innlandet with organisation number 980850234. The business is classified under market research and public opinion polling (NACE 73.200). The company was incorporated in 1999. Registered share capital is NOK 350,000, divided into 1400 shares. The company's stated purpose is: “Gjennomføring av markedsundersøkelser, rådgivning i markedsføring, samt det som naturlig hører inn under dette, herunder investering i andre selskaper innen samme kategori.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 181,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
▲ +7 %
Operating profit
NOK 181,000
▲ +69 %
Equity
NOK 324,000
▲ +3 %
Est. value
NOK 574,000

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
8.0%
Satisfactory
Return on total assets
Solidity
19.9%
Good
Equity as a share of total capital

Who owns MARKEDSINFO AS?

MARKEDSINFO AS
NOK 4.9m rev. · NOK 181,000 profit

MARKEDSINFO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MARKEDSINFO AS

Who owns MARKEDSINFO AS?

Bjørn Rune Stenberg is the largest registered owner, with 78.6%.

What is the revenue of MARKEDSINFO AS?

MARKEDSINFO AS had revenue of NOK 4.9m in 2024.

Who is the general manager of MARKEDSINFO AS?

Bjørn Rune Stenberg is registered as general manager of MARKEDSINFO AS.

Where is MARKEDSINFO AS based?

MARKEDSINFO AS has its business address in Hamar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.