BIZTRAC BETA
Translation and interpretation activities

LINGO ACCESS AS

Org. no. 982543371 Limited company (AS) Øygarden Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −69,000
Equity NOK 970,000
Incorporated 2000
Share capital NOK 40,000

Signals

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

LINGO ACCESS AS is registered as a limited company in Øygarden, Vestland with organisation number 982543371. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2000. Registered share capital is NOK 40,000, divided into 4024600 shares. The company's stated purpose is: “Levere språktjenester og kunne delta i andre selskaper. Yte undervisning og IT-support, samt kjøp/salg av tilhørende produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −69,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −69,000
Equity
NOK 970,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns LINGO ACCESS AS?

ROBERT GRYGIER
LINGO ACCESS AS
NOK 1.8m rev. · NOK −69,000 profit

LINGO ACCESS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LINGO ACCESS AS

Who owns LINGO ACCESS AS?

ROBERT GRYGIER is the largest registered owner, with 50.0%.

What is the revenue of LINGO ACCESS AS?

LINGO ACCESS AS had revenue of NOK 1.8m in 2025.

Who is the general manager of LINGO ACCESS AS?

Robert Grygier is registered as general manager of LINGO ACCESS AS.

Where is LINGO ACCESS AS based?

LINGO ACCESS AS has its business address in Straume.

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.