BIZTRAC BETA
COMPANY REGISTER PROFILE
911580373 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other education activities

LEKTOR JAKOBSEN AS

Org. no. 911580373 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2013
Share capital NOK 100,000

LEKTOR JAKOBSEN AS is registered as a limited company in Oslo, Oslo with organisation number 911580373. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 12000 shares. The company's stated purpose is: “Undervisning på nett og via klasserom. I tillegg kommer all annen nær beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 43,000

Financial health · 2024

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

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

Who owns LEKTOR JAKOBSEN AS?

MAGNUS MC KENZIE JAKOBSEN
LEKTOR JAKOBSEN AS
NOK 0 rev. · NOK 0 profit

LEKTOR JAKOBSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEKTOR JAKOBSEN AS

Who owns LEKTOR JAKOBSEN AS?

MAGNUS MC KENZIE JAKOBSEN is the largest registered owner, with 100.0%.

What is the revenue of LEKTOR JAKOBSEN AS?

LEKTOR JAKOBSEN AS had revenue of NOK 0 in 2024.

Who is the general manager of LEKTOR JAKOBSEN AS?

Magnus Mc Kenzie Jakobsen is registered as general manager of LEKTOR JAKOBSEN AS.

Where is LEKTOR JAKOBSEN AS based?

LEKTOR JAKOBSEN 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.