BIZTRAC BETA
Translation and interpretation activities

WORDINGLY AS

Org. no. 931337971 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK −50,000
Equity NOK 252,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−50k kr).

WORDINGLY AS is registered as a limited company in Bærum, Akershus with organisation number 931337971. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen oversettelse og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK −50,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK −50,000
Equity
NOK 252,000
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
41.3%
Very good
Equity as a share of total capital

Who owns WORDINGLY AS?

MARIKA SUNDLAND LEHTIMÄKI
WORDINGLY AS
NOK 1.4m rev. · NOK −50,000 profit

WORDINGLY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WORDINGLY AS

Who owns WORDINGLY AS?

MARIKA SUNDLAND LEHTIMÄKI is the largest registered owner, with 100.0%.

What is the revenue of WORDINGLY AS?

WORDINGLY AS had revenue of NOK 1.4m in 2025.

Who is the general manager of WORDINGLY AS?

Marika Sundland Lehtimäki is registered as general manager of WORDINGLY AS.

Where is WORDINGLY AS based?

WORDINGLY AS has its business address in Hosle.

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.