BIZTRAC BETA
Beverage serving activities

INSIDE VOSS AS

Org. no. 999615783 Limited company (AS) Voss Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 536,000
Equity NOK −201,000
Incorporated 2013
Employees 17
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−201k kr).

INSIDE VOSS AS is registered as a limited company in Voss, Vestland with organisation number 999615783. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2013 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets formål er drift av pub og diskotek samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 536,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 536,000
Equity
NOK −201,000
Est. value
NOK 4.0m

Financial health · 2024

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

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

Who owns INSIDE VOSS AS?

INSIDEGRUPPEN AS
INSIDE VOSS AS
NOK 7.1m rev. · NOK 536,000 profit

INSIDE VOSS AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about INSIDE VOSS AS

Who owns INSIDE VOSS AS?

INSIDEGRUPPEN AS is the largest registered owner, with 30.0%.

What is the revenue of INSIDE VOSS AS?

INSIDE VOSS AS had revenue of NOK 7.1m in 2024.

Who is the general manager of INSIDE VOSS AS?

Knut Larsen Holtekjølen is registered as general manager of INSIDE VOSS AS.

Where is INSIDE VOSS AS based?

INSIDE VOSS AS has its business address in Voss.

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.