BIZTRAC BETA
Photographic activities

LINE OWREN FOTOGRAFI AS

Org. no. 995250861 Limited company (AS) Stavanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 15,000
Equity NOK 181,000
Incorporated 2010
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

LINE OWREN FOTOGRAFI AS is registered as a limited company in Stavanger, Rogaland with organisation number 995250861. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fremstilling/salg av fotografier og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med liknende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 15,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 15,000
Equity
NOK 181,000
Est. value
NOK 181,000

Financial health · 2025

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

Who owns LINE OWREN FOTOGRAFI AS?

LINE OWREN
LINE OWREN FOTOGRAFI AS
NOK 1.2m rev. · NOK 15,000 profit

LINE OWREN FOTOGRAFI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINE OWREN FOTOGRAFI AS

Who owns LINE OWREN FOTOGRAFI AS?

LINE OWREN is the largest registered owner, with 100.0%.

What is the revenue of LINE OWREN FOTOGRAFI AS?

LINE OWREN FOTOGRAFI AS had revenue of NOK 1.2m in 2025.

Where is LINE OWREN FOTOGRAFI AS based?

LINE OWREN FOTOGRAFI AS has its business address in Stavanger.

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.