biztrac. BETA
COMPANY REGISTER PROFILE
997082761 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other educational support services n.e.c.

SPEAKLAB AS

Org. no. 997082761 Limited company (AS) Bergen Incorporated 2011 Active
Revenue 2025 NOK 5.7m
Operating profit NOK 157,000
Equity NOK 1.7m
Incorporated 2011
Employees 5
Share capital NOK 100,000

SPEAKLAB AS is registered as a limited company in Bergen, Vestland with organisation number 997082761. The business is classified under other educational support services n.e.c. (NACE 85.699). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kurs og undervisning innen kommunikasjon og formidling. Program og debattledelse samt annet som naturlig faller seg inn.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.7m in revenue and NOK 157,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.7m
▲ +3 %
Operating profit
NOK 157,000
▲ +419 %
Equity
NOK 1.7m
▲ +9 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
2.82
Very good
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
67.6%
Very good
Equity as a share of total capital

Who owns SPEAKLAB AS?

SPEAKLAB AS
NOK 5.7m rev. · NOK 157,000 profit

SPEAKLAB AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SPEAKLAB AS er morselskap for 1 datterselskap:

Frequently asked questions about SPEAKLAB AS

Who owns SPEAKLAB AS?

FAIRGATES AS is the largest registered owner, with 100.0%.

What is the revenue of SPEAKLAB AS?

SPEAKLAB AS had revenue of NOK 5.7m in 2025.

Who is the general manager of SPEAKLAB AS?

Siri Lill Mannes is registered as general manager of SPEAKLAB AS.

Where is SPEAKLAB AS based?

SPEAKLAB AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.