biztrac. BETA
COMPANY REGISTER PROFILE
933393887 ORG. NO. 2025 ACCOUNTS 11 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

LEKTER`N AS

Org. no. 933393887 Limited company (AS) Oslo Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 45.7m
Operating profit NOK 10.3m
Equity NOK 14.5m
Incorporated 1982
Employees 242
Share capital NOK 400,000

LEKTER`N AS is registered as a limited company in Oslo, Oslo with organisation number 933393887. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 1982 and has 242 registered employees. Registered share capital is NOK 400,000, divided into 10 shares. The company's stated purpose is: “Selv eller gjennom hel- eller deleide selskaper, å forestå restaurantvirksomhet, eiendomsdrift og investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.7m in revenue and NOK 10.3m in operating profit.

Former names: MAT & DRIKKE AS

Key figures · 2025

Revenue
NOK 45.7m
▼ −3 %
Operating profit
NOK 10.3m
▼ −3 %
Equity
NOK 14.5m
▼ −4 %
Est. value
NOK 38.1m

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
24.0%
Very good
Return on total assets
Solidity
26.0%
Good
Equity as a share of total capital

Who owns LEKTER`N AS?

LEKTER`N AS
NOK 45.7m rev. · NOK 10.3m profit

LEKTER`N AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LEKTER`N AS er morselskap for 7 datterselskaper:

Frequently asked questions about LEKTER`N AS

Who owns LEKTER`N AS?

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

What is the revenue of LEKTER`N AS?

LEKTER`N AS had revenue of NOK 45.7m in 2025.

Who is the general manager of LEKTER`N AS?

Tone Wicklund-Hansen is registered as general manager of LEKTER`N AS.

Where is LEKTER`N AS based?

LEKTER`N 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 03.10.2026.

Report a problem

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