BIZTRAC BETA
Beverage serving activities

ORANSJEVIN AS

Org. no. 916974515 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 89,000
Equity NOK −258,000
Incorporated 2016
Employees 6
Share capital NOK 252,000

Signals

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

ORANSJEVIN AS is registered as a limited company in Oslo, Oslo with organisation number 916974515. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2016 and has 6 registered employees. Registered share capital is NOK 252,000, divided into 252158 shares. The company's stated purpose is: “Drift av restaurant/pub, samt at selskapet også leier ut arbeidskraft, investere i eiendom og delta i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 89,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 89,000
Equity
NOK −258,000
Est. value
NOK 640,000

Financial health · 2024

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

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

Who owns ORANSJEVIN AS?

TORSHOV VINVEST AS
ORANSJEVIN AS
NOK 4.3m rev. · NOK 89,000 profit

ORANSJEVIN AS has 12 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORANSJEVIN AS

Who owns ORANSJEVIN AS?

TORSHOV VINVEST AS is the largest registered owner, with 27.6%.

What is the revenue of ORANSJEVIN AS?

ORANSJEVIN AS had revenue of NOK 4.3m in 2024.

Who is the general manager of ORANSJEVIN AS?

Thomas Tylman is registered as general manager of ORANSJEVIN AS.

Where is ORANSJEVIN AS based?

ORANSJEVIN AS has its business address in Oslo.

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.