BIZTRAC BETA
Intermediation service activities for courses and tutors

SPRÅKREISEBYRÅET AS

Org. no. 857482662 Limited company (AS) Oslo Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 255,000
Operating profit NOK −102,000
Equity NOK −1.4m
Incorporated 1990
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−102k kr).

SPRÅKREISEBYRÅET AS is registered as a limited company in Oslo, Oslo with organisation number 857482662. The business is classified under intermediation service activities for courses and tutors (NACE 85.610). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg av språkreiser og annen reisebyråvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 255,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2024

Revenue
NOK 255,000
Operating profit
NOK −102,000
Equity
NOK −1.4m

Financial health · 2024

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

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

Who owns SPRÅKREISEBYRÅET AS?

ADAM CHRISTOPHER WILTON
SPRÅKREISEBYRÅET AS
NOK 255,000 rev. · NOK −102,000 profit

SPRÅKREISEBYRÅET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPRÅKREISEBYRÅET AS

Who owns SPRÅKREISEBYRÅET AS?

ADAM CHRISTOPHER WILTON is the largest registered owner, with 100.0%.

What is the revenue of SPRÅKREISEBYRÅET AS?

SPRÅKREISEBYRÅET AS had revenue of NOK 255,000 in 2024.

Where is SPRÅKREISEBYRÅET AS based?

SPRÅKREISEBYRÅET 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.