BIZTRAC BETA
Translation and interpretation activities

TEGNSATT AS

Org. no. 931463829 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 163,000
Operating profit NOK 38,000
Equity NOK 53,000
Incorporated 2023
Share capital NOK 30,000

TEGNSATT AS is registered as a limited company in Kongsberg, Buskerud with organisation number 931463829. 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 varer og tjenester innen oversettelse og tolkning 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 163,000 in revenue and NOK 38,000 in operating profit.

Key figures · 2025

Revenue
NOK 163,000
Operating profit
NOK 38,000
Equity
NOK 53,000
Est. value
NOK 176,000

Financial health · 2024

Liquidity
2.12
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.8%
Weak
Equity as a share of total capital

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

Who owns TEGNSATT AS?

SARA ELISABETH VILLARROEL BERNTSEN
TEGNSATT AS
NOK 163,000 rev. · NOK 38,000 profit

TEGNSATT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEGNSATT AS

Who owns TEGNSATT AS?

SARA ELISABETH VILLARROEL BERNTSEN is the largest registered owner, with 100.0%.

What is the revenue of TEGNSATT AS?

TEGNSATT AS had revenue of NOK 163,000 in 2025.

Who is the general manager of TEGNSATT AS?

Sara Elisabeth Villarroel Berntsen is registered as general manager of TEGNSATT AS.

Where is TEGNSATT AS based?

TEGNSATT AS has its business address in Kongsberg.

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.