BIZTRAC BETA
Sports and recreation education

LARSHYBOY AS

Org. no. 814604772 Limited company (AS) Ås Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2,000
Equity NOK 161,000
Incorporated 2014
Share capital NOK 200,000

Signals

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

LARSHYBOY AS is registered as a limited company in Ås, Akershus with organisation number 814604772. The business is classified under sports and recreation education (NACE 85.510). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Tilby trening og kurs i Follo, samt kjøp og salg av aksjer i andre selskap innenfor trening, helse og velvære.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 161,000
Est. value
NOK 232,000

Financial health · 2025

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

Who owns LARSHYBOY AS?

LARS RANNOV KALLAND
LARSHYBOY AS
NOK 0 rev. · NOK −2,000 profit

LARSHYBOY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LARSHYBOY AS own?

LARSHYBOY AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LARSHYBOY AS

Who owns LARSHYBOY AS?

LARS RANNOV KALLAND is the largest registered owner, with 100.0%.

What is the revenue of LARSHYBOY AS?

LARSHYBOY AS had revenue of NOK 0 in 2025.

Who is the general manager of LARSHYBOY AS?

Lars Rannov Kalland is registered as general manager of LARSHYBOY AS.

Where is LARSHYBOY AS based?

LARSHYBOY AS has its business address in Vinterbro.

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.