BIZTRAC BETA
Wholesale of information and communication equipment

BUYLINK ØST AS

Org. no. 935665922 Limited company (AS) Hamar Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −20,000
Equity NOK 17,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BUYLINK ØST AS is registered as a limited company in Hamar, Innlandet with organisation number 935665922. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Salg og support av programvare knyttet til restaurant og detaljhandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 17,000
Est. value
NOK 21,000

Financial health · 2025

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

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

Who owns BUYLINK ØST AS?

EMIL ANDREAS MOKKELBOST ENGH
BUYLINK ØST AS
NOK 0 rev. · NOK −20,000 profit

BUYLINK ØST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BUYLINK ØST AS

Who owns BUYLINK ØST AS?

EMIL ANDREAS MOKKELBOST ENGH is the largest registered owner, with 51.0%.

What is the revenue of BUYLINK ØST AS?

BUYLINK ØST AS had revenue of NOK 0 in 2025.

Who is the general manager of BUYLINK ØST AS?

Martin Snekkerlien Moen is registered as general manager of BUYLINK ØST AS.

Where is BUYLINK ØST AS based?

BUYLINK ØST AS has its business address in Hamar.

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.