biztrac. BETA
COMPANY REGISTER PROFILE
922414661 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

FRK. LOVISE AS

Org. no. 922414661 Limited company (AS) Alstahaug Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK −71,000
Equity NOK 107,000
Incorporated 2019
Employees 20
Share capital NOK 30,000

Signals

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

FRK. LOVISE AS is registered as a limited company in Alstahaug, Nordland with organisation number 922414661. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kafé, bakeri og konditori i Sandnessjøen.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK −71,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
▲ +4 %
Operating profit
NOK −71,000
▼ −187 %
Equity
NOK 107,000
▼ −56 %
Est. value
NOK 124,000

Financial health · 2025

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
-9.0%
Not satisfactory
Return on total assets
Solidity
17.0%
Satisfactory
Equity as a share of total capital

Who owns FRK. LOVISE AS?

FRK. LOVISE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRK. LOVISE AS

Who owns FRK. LOVISE AS?

Ine-Eirin Freydis Jenssen Davidsen is the largest registered owner, with 33.3%.

What is the revenue of FRK. LOVISE AS?

FRK. LOVISE AS had revenue of NOK 4.9m in 2025.

Who is the general manager of FRK. LOVISE AS?

Hilde Anita Theimann Olsen is registered as general manager of FRK. LOVISE AS.

Where is FRK. LOVISE AS based?

FRK. LOVISE AS has its business address in Sandnessjøen.

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.