BIZTRAC BETA
Market research and public opinion polling

ANITA LYNNE AS

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

Signals

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

ANITA LYNNE AS is registered as a limited company in Oslo, Oslo with organisation number 913015738. The business is classified under market research and public opinion polling (NACE 73.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kvalitativ markedsanalyse og rådgivning, foruten forvaltning av selskapets kapital og ressurser i form av investeringsvirksomhet, deltakelse i andre selskaper, finansforvaltning og kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 1.0m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns ANITA LYNNE AS?

ANITA LYNNE
ANITA LYNNE AS
NOK 0 rev. · NOK −13,000 profit

ANITA LYNNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANITA LYNNE AS

Who owns ANITA LYNNE AS?

ANITA LYNNE is the largest registered owner, with 100.0%.

What is the revenue of ANITA LYNNE AS?

ANITA LYNNE AS had revenue of NOK 0 in 2025.

Who is the general manager of ANITA LYNNE AS?

Anita Lynne is registered as general manager of ANITA LYNNE AS.

Where is ANITA LYNNE AS based?

ANITA LYNNE 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.