biztrac. BETA
COMPANY REGISTER PROFILE
913017722 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of recreational and sports goods

LEXBERG.NO AS

Org. no. 913017722 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 495,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 30,000

LEXBERG.NO AS is registered as a limited company in Oslo, Oslo with organisation number 913017722. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Levere tjenester innen reiseformidling og andre tjenester som naturlig faller sammen med dette, herunder sykkelutleie, overnatting og behandling.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 495,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
▲ +48 %
Operating profit
NOK 495,000
▲ +42 %
Equity
NOK 1.1m
▲ +55 %
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
2.21
Very good
Current assets ÷ current liabilities
Profitability
34.2%
Very good
Return on total assets
Solidity
54.8%
Very good
Equity as a share of total capital

Who owns LEXBERG.NO AS?

LEXBERG.NO AS
NOK 3.3m rev. · NOK 495,000 profit

LEXBERG.NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LEXBERG.NO AS

Who owns LEXBERG.NO AS?

Rune Lennart Lexberg is the largest registered owner, with 100.0%.

What is the revenue of LEXBERG.NO AS?

LEXBERG.NO AS had revenue of NOK 3.3m in 2025.

Who is the general manager of LEXBERG.NO AS?

Rune Lennart Lexberg is registered as general manager of LEXBERG.NO AS.

Where is LEXBERG.NO AS based?

LEXBERG.NO 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.