biztrac. BETA
COMPANY REGISTER PROFILE
936512984 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

COZY TAVERN AS

Org. no. 936512984 Limited company (AS) Sveio Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 87,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

COZY TAVERN AS is registered as a limited company in Sveio, Vestland with organisation number 936512984. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av digitale spill og interaktiv underholdning.”. 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 87,000
Est. value
NOK 157,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns COZY TAVERN AS?

COZY TAVERN AS
NOK 0 rev. · NOK −13,000 profit

COZY TAVERN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COZY TAVERN AS

Who owns COZY TAVERN AS?

Malvin Halle Kvam is the largest registered owner, with 100.0%.

What is the revenue of COZY TAVERN AS?

COZY TAVERN AS had revenue of NOK 0 in 2025.

Who is the general manager of COZY TAVERN AS?

Malvin Halle Kvam is registered as general manager of COZY TAVERN AS.

Where is COZY TAVERN AS based?

COZY TAVERN AS has its business address in Sveio.

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.