BIZTRAC BETA
COMPANY REGISTER PROFILE
927538970 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

BARDRIFT MÅLØY AS

Org. no. 927538970 Limited company (AS) Kinn Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 322,000
Operating profit NOK 55,000
Equity NOK 226,000
Incorporated 2021
Share capital NOK 30,000

BARDRIFT MÅLØY AS is registered as a limited company in Kinn, Vestland with organisation number 927538970. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen barvirksomhet og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 322,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 322,000
Operating profit
NOK 55,000
Equity
NOK 226,000
Est. value
NOK 328,000

Financial health · 2025

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

Who owns BARDRIFT MÅLØY AS?

GUNN BØE
BARDRIFT MÅLØY AS
NOK 322,000 rev. · NOK 55,000 profit

BARDRIFT MÅLØY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARDRIFT MÅLØY AS

Who owns BARDRIFT MÅLØY AS?

GUNN BØE is the largest registered owner, with 100.0%.

What is the revenue of BARDRIFT MÅLØY AS?

BARDRIFT MÅLØY AS had revenue of NOK 322,000 in 2025.

Who is the general manager of BARDRIFT MÅLØY AS?

Gunn Bøe is registered as general manager of BARDRIFT MÅLØY AS.

Where is BARDRIFT MÅLØY AS based?

BARDRIFT MÅLØY AS has its business address in Måløy.

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.