biztrac. BETA
COMPANY REGISTER PROFILE
995727595 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

TEKSTUR OLRUD AS

Org. no. 995727595 Limited company (AS) Ringsaker Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 22,000
Equity NOK 218,000
Incorporated 2010
Employees 6
Share capital NOK 100,000

TEKSTUR OLRUD AS is registered as a limited company in Ringsaker, Innlandet with organisation number 995727595. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2010 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er frisørvirksomhet og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 22,000 in operating profit.

Former names: SALONG HÅRFAGRE AS

Key figures · 2025

Revenue
NOK 2.6m
▼ −4 %
Operating profit
NOK 22,000
▲ +121 %
Equity
NOK 218,000
▲ +9 %
Est. value
NOK 205,000

Financial health · 2025

Liquidity
1.32
Satisfactory
Current assets ÷ current liabilities
Profitability
3.1%
Weak
Return on total assets
Solidity
30.5%
Good
Equity as a share of total capital

Who owns TEKSTUR OLRUD AS?

TEKSTUR OLRUD AS
NOK 2.6m rev. · NOK 22,000 profit

TEKSTUR OLRUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEKSTUR OLRUD AS

Who owns TEKSTUR OLRUD AS?

Paal Hawk is the largest registered owner, with 100.0%.

What is the revenue of TEKSTUR OLRUD AS?

TEKSTUR OLRUD AS had revenue of NOK 2.6m in 2025.

Who is the general manager of TEKSTUR OLRUD AS?

Line Jevnaker is registered as general manager of TEKSTUR OLRUD AS.

Where is TEKSTUR OLRUD AS based?

TEKSTUR OLRUD AS has its business address in Furnes.

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.